2007-08-15 11:28:22 -03:00
|
|
|
:mod:`__future__` --- Future statement definitions
|
|
|
|
==================================================
|
|
|
|
|
|
|
|
.. module:: __future__
|
|
|
|
:synopsis: Future statement definitions
|
|
|
|
|
|
|
|
|
|
|
|
:mod:`__future__` is a real module, and serves three purposes:
|
|
|
|
|
|
|
|
* To avoid confusing existing tools that analyze import statements and expect to
|
|
|
|
find the modules they're importing.
|
|
|
|
|
|
|
|
* To ensure that future_statements run under releases prior to 2.1 at least
|
|
|
|
yield runtime exceptions (the import of :mod:`__future__` will fail, because
|
|
|
|
there was no module of that name prior to 2.1).
|
|
|
|
|
|
|
|
* To document when incompatible changes were introduced, and when they will be
|
|
|
|
--- or were --- made mandatory. This is a form of executable documentation, and
|
|
|
|
can be inspected programatically via importing :mod:`__future__` and examining
|
|
|
|
its contents.
|
|
|
|
|
|
|
|
Each statement in :file:`__future__.py` is of the form::
|
|
|
|
|
Merged revisions 61687-61688,61696,61700,61704-61705,61707-61709,61711-61712,61714-61716,61718-61722 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
r61687 | jeffrey.yasskin | 2008-03-21 06:02:44 +0100 (Fri, 21 Mar 2008) | 2 lines
Speed up test_signal from ~24s to 4s by avoiding nearly all of the sleep calls.
........
r61688 | jeffrey.yasskin | 2008-03-21 06:51:37 +0100 (Fri, 21 Mar 2008) | 5 lines
Try to fix test_signal breakages on Linux due to r61687. It appears that at
least two of the linux build bots aren't leaving zombie processes around for
os.waitpid to wait for, causing ECHILD errors. This would be a symptom of a bug
somewhere, but probably not in signal itself.
........
r61696 | georg.brandl | 2008-03-21 15:32:33 +0100 (Fri, 21 Mar 2008) | 2 lines
Mark the descitems in the tutorial as "noindex" so that :meth: cross-refs don't link to them.
........
r61700 | georg.brandl | 2008-03-21 18:19:29 +0100 (Fri, 21 Mar 2008) | 2 lines
Fix markup.
........
r61704 | jeffrey.yasskin | 2008-03-21 19:25:06 +0100 (Fri, 21 Mar 2008) | 3 lines
Try to fix test_signal on FreeBSD. I'm assuming that os.kill is failing to
raise a signal, but switching to subprocess makes the code cleaner anyway.
........
r61705 | jeffrey.yasskin | 2008-03-21 19:48:04 +0100 (Fri, 21 Mar 2008) | 7 lines
Speed test_threading up from 14s to .5s, and avoid a deadlock on certain
failures. The test for enumerate-after-join is now a little less rigorous, but
the bug it references says the error happened in the first couple iterations,
so 100 iterations should still be enough.
cProfile was useful for identifying the slow tests here.
........
r61707 | georg.brandl | 2008-03-21 20:14:38 +0100 (Fri, 21 Mar 2008) | 2 lines
Fix a code block in __future__ docs.
........
r61708 | georg.brandl | 2008-03-21 20:20:21 +0100 (Fri, 21 Mar 2008) | 2 lines
Add docs for __func__ and __self__ on methods.
........
r61709 | georg.brandl | 2008-03-21 20:37:57 +0100 (Fri, 21 Mar 2008) | 2 lines
Add docs for print_function and future_builtins. Fixes #2442.
........
r61711 | georg.brandl | 2008-03-21 20:54:00 +0100 (Fri, 21 Mar 2008) | 2 lines
#2136: allow single quotes in realm spec.
........
r61712 | georg.brandl | 2008-03-21 21:01:51 +0100 (Fri, 21 Mar 2008) | 3 lines
Issue #2432: give DictReader the dialect and line_num attributes
advertised in the docs.
........
r61714 | georg.brandl | 2008-03-21 21:11:46 +0100 (Fri, 21 Mar 2008) | 2 lines
#2358: add py3k warning to sys.exc_clear().
........
r61715 | georg.brandl | 2008-03-21 21:21:46 +0100 (Fri, 21 Mar 2008) | 2 lines
#2346/#2347: add py3k warning for __methods__ and __members__. Patch by Jack Diederich.
........
r61716 | georg.brandl | 2008-03-21 21:38:24 +0100 (Fri, 21 Mar 2008) | 2 lines
#2348: add py3k warning for file.softspace.
........
r61718 | georg.brandl | 2008-03-21 21:55:20 +0100 (Fri, 21 Mar 2008) | 2 lines
#2160: document PyImport_GetImporter.
........
r61719 | georg.brandl | 2008-03-21 21:55:51 +0100 (Fri, 21 Mar 2008) | 2 lines
Update doc ACKS.
........
r61720 | steven.bethard | 2008-03-21 22:01:18 +0100 (Fri, 21 Mar 2008) | 1 line
Replace hack in regrtest.py with use of sys.py3kwarning.
........
r61721 | georg.brandl | 2008-03-21 22:05:03 +0100 (Fri, 21 Mar 2008) | 2 lines
Add missing versionadded tag.
........
r61722 | christian.heimes | 2008-03-22 00:49:44 +0100 (Sat, 22 Mar 2008) | 3 lines
Applied patch #1657 epoll and kqueue wrappers for the select module
The patch adds wrappers for the Linux epoll syscalls and the BSD kqueue syscalls. Thanks to Thomas Herve and the Twisted people for their support and help.
TODO: Finish documentation documentation
........
2008-03-21 21:47:35 -03:00
|
|
|
FeatureName = _Feature(OptionalRelease, MandatoryRelease,
|
|
|
|
CompilerFlag)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
|
|
|
where, normally, *OptionalRelease* is less than *MandatoryRelease*, and both are
|
|
|
|
5-tuples of the same form as ``sys.version_info``::
|
|
|
|
|
|
|
|
(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
|
|
|
|
PY_MINOR_VERSION, # the 1; an int
|
|
|
|
PY_MICRO_VERSION, # the 0; an int
|
|
|
|
PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
|
|
|
|
PY_RELEASE_SERIAL # the 3; an int
|
|
|
|
)
|
|
|
|
|
|
|
|
*OptionalRelease* records the first release in which the feature was accepted.
|
|
|
|
|
|
|
|
In the case of a *MandatoryRelease* that has not yet occurred,
|
|
|
|
*MandatoryRelease* predicts the release in which the feature will become part of
|
|
|
|
the language.
|
|
|
|
|
|
|
|
Else *MandatoryRelease* records when the feature became part of the language; in
|
|
|
|
releases at or after that, modules no longer need a future statement to use the
|
|
|
|
feature in question, but may continue to use such imports.
|
|
|
|
|
|
|
|
*MandatoryRelease* may also be ``None``, meaning that a planned feature got
|
|
|
|
dropped.
|
|
|
|
|
|
|
|
Instances of class :class:`_Feature` have two corresponding methods,
|
|
|
|
:meth:`getOptionalRelease` and :meth:`getMandatoryRelease`.
|
|
|
|
|
|
|
|
*CompilerFlag* is the (bitfield) flag that should be passed in the fourth
|
|
|
|
argument to the builtin function :func:`compile` to enable the feature in
|
|
|
|
dynamically compiled code. This flag is stored in the :attr:`compiler_flag`
|
|
|
|
attribute on :class:`_Feature` instances.
|
|
|
|
|
|
|
|
No feature description will ever be deleted from :mod:`__future__`.
|
|
|
|
|