@@ -56,7 +56,7 @@ Python 2.6 incorporates new features and syntax from 3.0 while
56
56
remaining compatible with existing code by not removing older features
57
57
or syntax. When it's not possible to do that, Python 2.6 tries to do
58
58
what it can, adding compatibility functions in a
59
- :mod: `future_builtins ` module and a :option: `!-3 ` switch to warn about
59
+ :mod: `! future_builtins ` module and a :option: `!-3 ` switch to warn about
60
60
usages that will become unsupported in 3.0.
61
61
62
62
Some significant new packages have been added to the standard library,
109
109
Python 3.0 adds several new built-in functions and changes the
110
110
semantics of some existing builtins. Functions that are new in 3.0
111
111
such as :func: `bin ` have simply been added to Python 2.6, but existing
112
- builtins haven't been changed; instead, the :mod: `future_builtins `
112
+ builtins haven't been changed; instead, the :mod: `! future_builtins `
113
113
module has versions with the new 3.0 semantics. Code written to be
114
114
compatible with 3.0 can do ``from future_builtins import hex, map `` as
115
115
necessary.
@@ -2739,13 +2739,13 @@ numbers.
2739
2739
2740
2740
.. ======================================================================
2741
2741
2742
- The :mod: `future_builtins ` module
2742
+ The :mod: `! future_builtins ` module
2743
2743
--------------------------------------
2744
2744
2745
2745
Python 3.0 makes many changes to the repertoire of built-in
2746
2746
functions, and most of the changes can't be introduced in the Python
2747
2747
2.x series because they would break compatibility.
2748
- The :mod: `future_builtins ` module provides versions
2748
+ The :mod: `! future_builtins ` module provides versions
2749
2749
of these built-in functions that can be imported when writing
2750
2750
3.0-compatible code.
2751
2751
0 commit comments