Update about on-demand creation.
This commit is contained in:
parent
b1c944fbd2
commit
ceadcf5f92
15
pep-3147.txt
15
pep-3147.txt
|
@ -262,7 +262,8 @@ Case 5: read-only file systems
|
|||
|
||||
When the source lives on a read-only file system, or the `__pycache__`
|
||||
directory or pyc file cannot otherwise be written, all the same rules
|
||||
apply.
|
||||
apply. This is also the case when `__pycache__` happens to be written
|
||||
with permissions which do not allow for writing containing pyc files.
|
||||
|
||||
|
||||
|
||||
|
@ -569,6 +570,18 @@ in better with future possible use cases such as JIT output from
|
|||
Unladen Swallow.
|
||||
|
||||
|
||||
On-demand creation
|
||||
------------------
|
||||
|
||||
The original use case was to support multiple versions of Python on
|
||||
the same system. This could be accomplished solely through
|
||||
pre-creation of `__pycache__` directories during the compilation phase
|
||||
of installation, without also supporting on-demand creation of the
|
||||
`__pycache__` directories. It seems however the consensus to be that
|
||||
on-demand creation is useful enough to keep since it reduces clutter
|
||||
in source directories.
|
||||
|
||||
|
||||
References
|
||||
==========
|
||||
|
||||
|
|
Loading…
Reference in New Issue