On Dec 13, 6:03 am, Steve Holden wrote:
> Poor Yorick wrote:
> > I have a future statement in a script which is intended to work in 2.6 and
> > 3.
> > Shouldn't compile flags in __future__ objects essentially be noops for
> > versions
> > that already support the feature? doctest is complaining
Poor Yorick wrote:
> I have a future statement in a script which is intended to work in 2.6 and 3.
> Shouldn't compile flags in __future__ objects essentially be noops for
> versions
> that already support the feature? doctest is complaining about unrecognised
> flags. This illustrates the proble
I have a future statement in a script which is intended to work in 2.6 and 3.
Shouldn't compile flags in __future__ objects essentially be noops for versions
that already support the feature? doctest is complaining about unrecognised
flags. This illustrates the problem:
Python 3.0 (r30:67507,
