what gives with

[Benjamin Peterson]

Darren Dale <dsdale24 <at> 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
> python-2.5 I cant import my package. What is the point of providing
> absolute_import in __future__ if the api is completely different than
> the implementation in future python versions? Its bizarre.

The API is not completely different. The 2.5 version of the feature just lacks
the ability to import with "*". It is still same in 2.6, but with the ability to
use "*".