Poor Yorick wrote:
I have a future statement in a script I intend to work on 2.6 and 3. Shouldn't
__future__ statements basically be noops for versions that already support the
feature? doctest is complaining about compiler flags. This illustrates the
problem:
Python 3.0 (r30:67507, Dec
I have a future statement in a script I intend to work on 2.6 and 3. Shouldn't
__future__ statements basically be noops for versions that already support the
feature? doctest is complaining about compiler flags. This illustrates the
problem:
Python 3.0 (r30:67507, Dec 3 2008, 20:14:27) [
