Darren Dale gmail.com> writes:
> I was talking about the behavior after doing "from __future__ import
> absolute_import". I've been developing on python-2.6 using
> absolute_import for weeks, knowing that I could do "from __future__
> import absolute import" on python-2.5. Now when I try to use
>
Darren Dale wrote:
What is the point of providing absolute_import in __future__ if the
api is completely different than the implementation in future python versions?
The point is to obtain user experience with a proposed feature _before_
you fix the interface and start having to be "backwa
Darren Dale wrote:
> On Jan 22, 10:07 pm, Benjamin Peterson wrote:
>> Darren Dale gmail.com> writes:
>>
>>> Judging fromhttp://bugs.python.org/issue2400, this issue
>>> was fixed back in May 2008, but it is still present with python-2.5.4,
>>> which was released in December. Why wont python-2.5 a
On Jan 22, 10:07 pm, Benjamin Peterson wrote:
> Darren Dale gmail.com> writes:
>
> > Judging fromhttp://bugs.python.org/issue2400, this issue
> > was fixed back in May 2008, but it is still present with python-2.5.4,
> > which was released in December. Why wont python-2.5 allow this kind of
> > i
Darren Dale gmail.com> writes:
> Judging from http://bugs.python.org/issue2400 , this issue
> was fixed back in May 2008, but it is still present with python-2.5.4,
> which was released in December. Why wont python-2.5 allow this kind of
> import?
Allowing that would be a new feature which is dis
I know the use of "from foo import *" is discouraged, but I'm writing
a package that I hope others may want to integrate as a subpackage of
their own projects, I know what I'm doing, and I want to use the
"from .bar import *" syntax internally. It works fine with python-2.6,
but with python-2.5 I g
