The historic reason is that we supported running both w/ the std lib and without. I don't think that's really a concern so the fake __future__ could be replaced with the real one from the std lib.
From: ironpython-users-bounces+dinov=microsoft....@python.org [mailto:ironpython-users-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 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/IronPython/IronPython/Lib It IS the correct __future__.py in the External.LCA_RESTRICTED/Languages/IronPython/27/Lib version though. When I copied the version from there to the other location, doctest ran correctly, so I was just wondering if there was something else that required a different __future__.py. Thanks, slide -- Website: http://earl-of-code.com
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org http://mail.python.org/mailman/listinfo/ironpython-users
