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

spelling

This commit is contained in:
David Goodger 2003-01-23 18:51:09 +00:00
parent f6324c80f8
commit 7d8ea82a4c
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0304.txt
View File

@ -46,7 +46,7 @@ is:
of bytecode files is suppressed altogether.
After startup, all runtime references are to sys.pythonbytecodebase,
not the PYTHONBYTECODEBASE enbironment variable. sys.path is not
not the PYTHONBYTECODEBASE environment variable. sys.path is not
modified.
@ -147,7 +147,7 @@ circumstances. If the directory is writable, nearly simultaneous
attempts attempts to write the bytecode file by two separate processes
may occur, resulting in file corruption. [4]_
In environments with ramdisks available, it may be desirable for
In environments with RAM disks available, it may be desirable for
performance reasons to write bytecode files to a directory on such a
disk. Similarly, in environments where Python source code resides on
network file systems, it may be desirable to cache bytecode files on
@ -247,7 +247,7 @@ not writable by the current user.
file is written to the augmented directory. Intermediate
directories will be created as needed.
- At startuyp PYTHONBYTECODEBASE is set to ``TEMP`` and the current
- At startup PYTHONBYTECODEBASE is set to ``TEMP`` and the current
working directory at application startup is ``H:\NET``. The
potential bytecode base is thus ``H:\NET\TEMP``. If this directory
exists and is writable by the current user, sys.pythonbytecodebase