On Wed, Jan 1, 2014 at 4:42 PM, Pawel Jasinski wrote:
> hi,
>
> There is a special version of __future__.py in
> IronLanguages/Languages/IronPython/IronPython/Lib which is getting in
> my way when running out of the development environment.
>
> I wonder why is it there?
Historical reasons, maybe?
hi,
There is a special version of __future__.py in
IronLanguages/Languages/IronPython/IronPython/Lib which is getting in
my way when running out of the development environment.
I wonder why is it there?
--pawel
___
Ironpython-users mailing list
Ironpyt
rs-bounces+dinov=microsoft@python.org] On Behalf Of
Slide
Sent: Tuesday, March 13, 2012 8:53 PM
To: ironpython-users@python.org
Subject: [Ironpython-users] __future__.py
Jeff or Dino (or anyone else who might knows),
Is there any specific reason we aren't using the __future__.py directly f
Jeff or Dino (or anyone else who might knows),
Is there any specific reason we aren't using the __future__.py directly
from the stdlib? I ran into an issue today with doctest when it was
extracting future flags, nested_scopes was not defined in the __future__.py
that is located at Languages/IronPy
