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

Make names in __future__.py bind to class instances instead of 2-tuples. 

Suggested on c.l.py by William Tanksley, and I like it.
This commit is contained in:
Tim Peters 2001-03-02 02:53:08 +00:00
parent 77c92df29b
commit b6893e3c49
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pep-0236.txt
View File

@ -165,11 +165,7 @@ Standard Module __future__.py
Each statment in __future__.py is of the form: Each statment in __future__.py is of the form:
FeatureName = ReleaseInfo FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease) ")"
ReleaseInfo is a pair of the form:
(OptionalRelease, MandatoryRelease)
where, normally, OptionalRelease < MandatoryRelease, and both are where, normally, OptionalRelease < MandatoryRelease, and both are
5-tuples of the same form as sys.version_info: 5-tuples of the same form as sys.version_info:
@ -201,11 +197,14 @@ Standard Module __future__.py
MandatoryRelease may also be None, meaning that a planned feature got MandatoryRelease may also be None, meaning that a planned feature got
dropped. dropped.
No line will ever be deleted from __future__.py. Instances of class _Feature have two corresponding methods,
.getOptionalRelease() and .getMandatoryRelease().
No feature line will ever be deleted from __future__.py.
Example line: Example line:
nested_scopes = (2, 1, 0, "beta", 1), (2, 2, 0, "final", 0) nested_scopes = _Feature((2, 1, 0, "beta", 1), (2, 2, 0, "final", 0))
This means that This means that