Jeff or Dino (or anyone else who might knows),<div><br></div><div>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</div>
<div><br></div><div>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.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>slide<br clear="all"><div><br></div>-- <br>Website: <a href="http://earl-of-code.com" target="_blank">http://earl-of-code.com</a><br>
</div>