Skip to content
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

Open
KOLANICH opened this issue Sep 29, 2017 · 3 comments

Comments

@KOLANICH
Copy link

commented Sep 29, 2017

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 formay. Why don't we have the things which are part of setup.cfg standardized too?

So I propose to
0 ship setuptools with python
1 merge setup.cfg into pyproject.toml and publish a PEP
2 setuptools should be workable without setup.py, only with pyproject.toml in a repo
3 pyproject.toml is the primary source of metainfo. setup.py should be executed if and only if pyproject.toml uses any variables from it.
4 Write a warning in red that setup.py is deprecated each time setuptools.setup is used

@ghost

This comment has been minimized.

Copy link

commented Sep 29, 2017

0 ship setuptools with python

Not going to happen. In fact, we're discussing moving distutils into setuptools (@jaraco, see distutils-sig).

@tuukkamustonen

This comment has been minimized.

Copy link

commented Oct 19, 2017

1 merge setup.cfg into pyproject.toml and publish a PEP

Just noting that setup.cfg is being used also by several other tools like flake8, pytest, etc.

4 pyproject.toml is the primary source of metainfo. setup.py should be executed if and only if it pyproject.toml uses some variables from it.

Care to elaborate how would pyproject.toml use variables from setup.py?

@RonnyPfannschmidt

This comment has been minimized.

Copy link
Contributor

commented May 27, 2018

as things currently are, setup.py is the entrypoint and could use variables from pyproject.toml

i propose starting with a tool.setuptools.opptions section for putting plain setup.py parameters

a tool.setuptools.metadata for the plain metadata sections and tool.setuptools.comands for commands/aliases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.