[IPython-user] More ipython and python2.5: 'with' statements

[Zachary Pincus]

The actual 'with' case isn't too huge an issue -- but it could  
possibly be indicative of a larger problem.

Nothing in the python 2.5 standard lib appears to explicitly import  
anything from __future__, so the with_statement must be coming in  
another way. I have no idea if that way is a problem in ipython, but  
I thought I'd mention it in case it rang any bells with any ipython  
developers.

Oh well.

On Mar 10, 2006, at 12:04 AM, Ville Vainio wrote:

> On 3/10/06, Fernando Perez <Fernando.Perez at colorado.edu> wrote:
>
>> but you have to keep in mind that ipython imports a ton of modules  
>> from the
>> standard library.  I wonder if, in 2.5, any of the stdlib modules  
>> have these
>> future imports, which would explain the behavior you are seeing.
>
> Shouldn't the effect of future statement be limited to the current  
> file?
>
> In any case, I don't see this as a huge problem... interactive use can
> be quite strict about what is reserved, "breaking code" does not
> matter if the code that got broken was authored 0.5 seconds ago. :-)
>
> --
> Ville Vainio - vivainio.googlepages.com
> vainio.blogspot.com - g[mail | talk]='vivainio'