iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Explain why we didn't use setup.cfg (#667)

This commit is contained in:
Brett Cannon 2018-06-01 17:29:36 -07:00 committed by GitHub
parent 700b1c6b0e
commit da09c9243a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pep-0518.txt
View File

@ -375,6 +375,17 @@ An example Python literal file for the proposed data would be::
} }
Sticking with ``setup.cfg``
---------------------------
There are two issues with ``setup.cfg`` used by setuptools as a general
format. One is that they are ``.ini`` files which have issues as mentioned
in the configparser_ discussion above. The other is that the schema for
that file has never been rigourlessly defined and thus it's unknown which
format would be safe to use going forward without potentially confusing
setuptools installations.
Other file names Other file names
---------------- ----------------