Add question about timing of 3.0.
This commit is contained in:
parent
e6393b6fd8
commit
560f0fe45a
12
pep-0238.txt
12
pep-0238.txt
|
@ -375,6 +375,18 @@ Open Issues
|
||||||
|
|
||||||
FAQ
|
FAQ
|
||||||
|
|
||||||
|
Q. When will Python 3.0 be released?
|
||||||
|
|
||||||
|
A. We don't plan that long ahead, so we can't say for sure. We
|
||||||
|
want to allow at least two years for the transition. If Python
|
||||||
|
3.0 comes out sooner, we'll keep the 2.x line alive for
|
||||||
|
backwards compatibility until at least two years from the
|
||||||
|
release of Python 2.2. In practice, you will be able to
|
||||||
|
continue to use the Python 2.x line for several years after
|
||||||
|
Python 3.0 is released, so you can take your time with the
|
||||||
|
transition. Sites are expected to have both Python 2.x and
|
||||||
|
Python 3.x installed simultaneously.
|
||||||
|
|
||||||
Q. Why isn't true division called float division?
|
Q. Why isn't true division called float division?
|
||||||
|
|
||||||
A. Because I want to keep the door open to *possibly* introducing
|
A. Because I want to keep the door open to *possibly* introducing
|
||||||
|
|
Loading…
Reference in New Issue