-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge setup.cfg spec with pyproject.toml one and deprecate setup.py and setup.cfg #1160
Comments
Not going to happen. In fact, we're discussing moving distutils into setuptools (@jaraco, see distutils-sig). |
Just noting that
Care to elaborate how would pyproject.toml use variables from setup.py? |
as things currently are, setup.py is the entrypoint and could use variables from i propose starting with a a |
I'm going to close this in favor of #1688. We are not going to deprecate |
https://setuptools.readthedocs.io/en/latest/userguide/commands.html#test-build-package-and-run-a-unittest-suite https://setuptools.readthedocs.io/en/latest/userguide/dependency_management.html#optional-dependencies https://tox.readthedocs.io/en/latest/example/basic.html#integration-with-setup-py-test-command https://pytest-runner.readthedocs.io/en/latest/#deprecation-notice pypa/setuptools#1160 pypa/setuptools#1684 pypa/setuptools#931 pytest-dev/pytest-runner@78a492c PyCQA/flake8#1098 PyCQA/flake8@4b72089
https://setuptools.readthedocs.io/en/latest/userguide/commands.html#test-build-package-and-run-a-unittest-suite https://setuptools.readthedocs.io/en/latest/userguide/dependency_management.html#optional-dependencies https://tox.readthedocs.io/en/latest/example/basic.html#integration-with-setup-py-test-command https://pytest-runner.readthedocs.io/en/latest/#deprecation-notice pypa/setuptools#1160 pypa/setuptools#1684 pypa/setuptools#931 pytest-dev/pytest-runner@78a492c PyCQA/flake8#1098 PyCQA/flake8@4b72089
Now we have a bunch of files. It's a mess:
1 python packages metadata is in fact generated by
setup.py
script. This means if you need to parse it you'll have to execute the script.2 Recently
pyproject.toml
was introduced, which contains for now only the description of the packages needed to build a package and data in backend-specific format. Why don't we have the things which are part ofsetup.cfg
standardized too?So I propose to
0 ship setuptools with python. I mean preinstall it as if it was installed by pip.
1 integrate
setup.cfg
spec intopyproject.toml
and publish a PEP2 setuptools should be workable without
setup.py
, only withpyproject.toml
in a dir3
pyproject.toml
is the primary source of metainfo.setup.py
should be executed if and only ifpyproject.toml
uses any variables from it.4 Write a warning in red that setup.py is deprecated each time
setuptools.setup
is usedThe text was updated successfully, but these errors were encountered: