On Wed, 2008-11-26 at 17:42 +0000, vila wrote:
> You can Use The Source James :) __future__ is a regular python package,
> I don't have a python3k handy but I'm pretty sure the package is still
> there. After all it exists to ensure forward compatibility, it will be a
> bit strange that it can break backward compatibility.
Ah, I didn't know that it was a regular package, I thought it was done
via some magic.
> By the way, what is the rationale with checking imports from __future__
> ? Do you have examples where it break things ?
On Wed, 2008-11-26 at 17:42 +0000, vila wrote:
> You can Use The Source James :) __future__ is a regular python package,
> I don't have a python3k handy but I'm pretty sure the package is still
> there. After all it exists to ensure forward compatibility, it will be a
> bit strange that it can break backward compatibility.
Ah, I didn't know that it was a regular package, I thought it was done
via some magic.
> By the way, what is the rationale with checking imports from __future__
> ? Do you have examples where it break things ?
I don't know, I was just asked to report this.
Thanks,
James