PEP 648: grammar tweaks
This commit is contained in:
parent
de02973f85
commit
9cf3171f43
|
@ -159,7 +159,7 @@ Interaction with virtual environments
|
|||
-------------------------------------
|
||||
|
||||
The customizations applied to an interpreter via the new
|
||||
``__sitecustomize__`` solutions will continue to work when an user creates a
|
||||
``__sitecustomize__`` solutions will continue to work when a user creates a
|
||||
virtual environment the same way that ``sitecustomize.py``
|
||||
interact with virtual environments.
|
||||
|
||||
|
@ -218,7 +218,7 @@ Support in build backends
|
|||
Whilst build backends can choose to provide an option to facilitate the
|
||||
installation of these files into a ``__sitecustomize__`` directory, this
|
||||
PEP does not address that directly. Similar to ``pth`` files, build backends
|
||||
can choose to not provide an easy to configure mechanism for
|
||||
can choose to not provide an easy-to-configure mechanism for
|
||||
``__sitecustomize__`` files and let users hook into the installation
|
||||
process to include such files. We do not think build backends enhanced
|
||||
support as a requirement for this PEP.
|
||||
|
@ -316,7 +316,7 @@ Security implications
|
|||
---------------------
|
||||
|
||||
This PEP aims to move all code execution from ``pth`` files to files within a
|
||||
``__customize__`` directory. We think this is an improvement to system admins
|
||||
``__sitecustomize__`` directory. We think this is an improvement to system admins
|
||||
for the following reasons:
|
||||
|
||||
* Allows to quickly identify the code being executed at startup time by the
|
||||
|
|
Loading…
Reference in New Issue