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

Spell-checked.

This commit is contained in:
Barry Warsaw 2012-05-25 14:13:23 -04:00
parent c9a869d496
commit 30f90b96c0
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
pep-0421.txt
View File

@ -52,8 +52,7 @@ Proposal
We will add a new attribute to the ``sys`` module, called
``sys.implementation``, as an object with attribute-access (as opposed
to a mapping). It will contain contain implementation-specific
information.
to a mapping). It will contain implementation-specific information.
The attributes of this object will remain fixed during interpreter
execution and through the course of an implementation version. This
@ -72,7 +71,7 @@ with discretion, as described in `Adding New Required Attributes`_.
While this PEP places no other constraints on ``sys.implementation``,
it also recommends that no one rely on capabilities outside those
described here. The only exception to that recommendation is for
attributes starting with an underscore. Implementors may use those
attributes starting with an underscore. Implementers may use those
as appropriate to store per-implementation data.
@ -84,7 +83,7 @@ library and language definition will rely, meaning implementers must
define them:
**name**
A lower-case identifer representing the implementation. Examples
A lower-case identifier representing the implementation. Examples
include 'pypy', 'jython', 'ironpython', and 'cpython'.
**version**
@ -117,7 +116,7 @@ All proposals for new required attributes will go through the normal
PEP process. Such a PEP need not be long, just long enough. It will
need to sufficiently spell out the rationale for the new attribute,
its use cases, and the impact it will have on the various Python
implemenations.
implementations.
Version Format
@ -295,7 +294,7 @@ The Problem With ``sys.(version|version_info|hexversion)``
Earlier versions of this PEP made the mistake of calling
``sys.version_info`` (and friends) the version of the Python language,
in contrast to the implementation. However, this is not the case.
Instead, it is the version of the CPython implementation. Incidently,
Instead, it is the version of the CPython implementation. Incidentally,
the first two components of ``sys.version_info`` (major and minor) also
reflect the version of the language definition.
@ -311,7 +310,7 @@ implementation will definitely help to clarify the distinction from the
language version.
Feedback From Other Python Implementors
Feedback From Other Python Implementers
=======================================
IronPython
@ -386,7 +385,7 @@ small as possible.
However, as already noted, many other efforts predate
``sys.implementation``. Neither is it necessarily a major part of the
effort. Rather, consider it as part of the infrastructure of the
effort to make Python friendler to alternate implementations.
effort to make Python friendlier to alternate implementations.
Alternatives