Georg Brandl wrote:
> This is a bug and has now been fixed in the SVN repo.
> Thanks for bringing it up.
Ouch, I feel bad now. I've been noticing this behavior since 2.5B1 but
I didn't realize it was a bug.
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> My understanding of the __future__ statement is that you may say
> something like:
>
> from __future__ import foo, bar
>
> to enable more than one feature. However, this does not seem to be
> working properly in 2.5; it behaves as expected when typed into the
> interac
[EMAIL PROTECTED] wrote:
> My understanding of the __future__ statement is that you may say
> something like:
>
> from __future__ import foo, bar
>
> to enable more than one feature. However, this does not seem to be
> working properly in 2.5; it behaves as expected when typed into the
> interacti
My understanding of the __future__ statement is that you may say
something like:
from __future__ import foo, bar
to enable more than one feature. However, this does not seem to be
working properly in 2.5; it behaves as expected when typed into the
interactive interpreter, but not when it is in a
