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

Add note about fresh subprocess per build (#308)

This commit is contained in:
Thomas Kluyver 2017-07-15 06:31:54 +02:00 committed by Nick Coghlan
parent 36212596ba
commit ea76e4431b
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0517.txt
View File

@ -318,6 +318,9 @@ If not defined, the default implementation is equivalent to ``return []``.
pick how to make an editable install? And if the frontend does, what does it pick how to make an editable install? And if the frontend does, what does it
need from the backend to do so. need from the backend to do so.
Config settings
===============
:: ::
config_settings config_settings
@ -425,6 +428,10 @@ meets the above criteria. In particular, it MUST NOT assume that it
has access to any packages except those that are present in the has access to any packages except those that are present in the
stdlib, or that are explicitly declared as build-requirements. stdlib, or that are explicitly declared as build-requirements.
Frontends should call each hook in a fresh subprocess, so that backends are
free to change process global state (such as environment variables or the
working directory). A Python library will be provided which frontends can use
to easily call hooks this way.
Recommendations for build frontends (non-normative) Recommendations for build frontends (non-normative)
--------------------------------------------------- ---------------------------------------------------