# PEP 621: round 3

**URL:** <https://discuss.python.org/t/pep-621-round-3/5472>\
**Category:** Packaging\
**Created:** [October 18, 2020, 8:57pm UTC](https://discuss.python.org/t/pep-621-round-3/5472 "2020-10-18T20:57:42Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ofek](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ofek/32/1033_2.png) [@ofek](https://discuss.python.org/u/ofek)\
**Post date:** [October 20, 2020, 12:51am UTC](https://discuss.python.org/t/pep-621-round-3/5472/7 "2020-10-20T00:51:59Z")

</div>

I don’t strongly object to the changes, but agree with Paul that this was extremely unexpected.

My concerns:

1. We should try to immediately get TOML support in the standard library. Until then, we should recommend a library so installs don’t pull in more than one of `toml`, `tomlkit`, etc.

2. We should be much more explicit regarding the new `sdist` requirements. For example, backends would have to remove the `dynamic` field after each entry is made static, right?

3. 

> [@brettcannon](#):
>
> To me, an sdist is a post-source artifact, not a pre-wheel artifact

That is contrary to what most people say here: [Purpose of an sdist](https://discuss.python.org/t/purpose-of-an-sdist/4639)

Question: does `pip` treat an `sdist` as something that is installed directly or does it build a `wheel` from it first? It has been a while since I looked at the code.

---

_[View the full topic](https://discuss.python.org/t/pep-621-round-3/5472)._