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

PEP 516: Resolve uses of the default role (#3400)

This commit is contained in:
Adam Turner 2023-09-01 20:27:51 +01:00 committed by GitHub
parent 76159afb05
commit 87d13e4169
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
pep-0516.txt
View File

@ -216,9 +216,10 @@ develop [--prefix PREFIX]
flit develop --root /tmp/ --prefix /usr/local
Should install scripts within `/tmp/usr/local/bin`, even if the Python
environment in use reports that the sys.prefix is `/usr/` which would lead
to using `/tmp/usr/bin/`. Similar logic applies for package files etc.
Should install scripts within ``/tmp/usr/local/bin``, even if the Python
environment in use reports that the sys.prefix is ``/usr/`` which would
lead to using ``/tmp/usr/bin/``.
Similar logic applies for package files etc.
The build environment
---------------------
@ -307,15 +308,15 @@ When 'pip' reads this it would prepare an environment with flit in it before
trying to use flit.
Because flit doesn't have setup-requires support today,
`flit build_requires` would just output a constant string::
``flit build_requires`` would just output a constant string::
{"build_requires": []}
`flit metadata` would interrogate `flit.ini` and marshal the metadata into
``flit metadata`` would interrogate ``flit.ini`` and marshal the metadata into
a wheel METADATA file and output that on stdout.
`flit wheel` would need to accept a `-d` parameter that tells it where to output the
wheel (pip needs this).
``flit wheel`` would need to accept a ``-d`` parameter that tells it where to
output the wheel (pip needs this).
Backwards Compatibility
=======================
@ -349,7 +350,7 @@ run by pip, and that will try and fail to install A.
As such we recommend that tools which are currently used as setup-requires
either ensure that they keep a `setuptools shim`_ or find their consumers and
get them all to upgrade to the use of a `pypa.json` in advance of moving
get them all to upgrade to the use of a ``pypa.json`` in advance of moving
themselves. Pragmatically that is impossible, so the advice is to keep a
setuptools shim indefinitely - both for projects like pbr, setuptools_scm and
also projects like numpy.