You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tutorial still mentions that either have to use setup.py or setup.cfg to store your metadata.
Configuring metadata
There are two types of metadata: static and dynamic.
Static metadata (setup.cfg): guaranteed to be the same every time. This is simpler, easier to read, and avoids many common errors, like encoding errors.
Dynamic metadata (setup.py): possibly non-deterministic. Any items that are dynamic or determined at install-time, as well as extension modules or extensions to setuptools, need to go into setup.py.
Static metadata (setup.cfg) should be preferred. Dynamic metadata (setup.py) should be used only as an escape hatch when absolutely necessary. setup.py used to be required, but can be omitted with newer versions of setuptools and pip.
I believe this is not true anymore and all of those can now be stored in pyproject.yaml. I wonder if this can be fixed now or if there's a timeline or a required milestone before setup.py and setup.cfg can be removed in favour for pyproject.toml.
The text was updated successfully, but these errors were encountered:
I asked for confirmation in pypa/setuptools#2671 (comment), but my understanding is that it is okay to just use pyproject.toml for core metadata (with the caveat that more complex configurations are still experimental or unsupported).
The tutorial still mentions that either have to use setup.py or setup.cfg to store your metadata.
I believe this is not true anymore and all of those can now be stored in pyproject.yaml. I wonder if this can be fixed now or if there's a timeline or a required milestone before setup.py and setup.cfg can be removed in favour for pyproject.toml.
The text was updated successfully, but these errors were encountered: