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 of setup.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 into pyproject.toml and publish a PEP
2 setuptools should be workable without setup.py, only with pyproject.toml in a dir
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
tuukkamustonen, drunkwcodes, ankostis, dmpe, feluxe and 1 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4