PEP 328 says that 
from __future__ import absolute_import

will be part of Python 2.4, but it is not:

D:\Projects\CB>python
Python 2.4 (#60, Nov 30 2004, 11:49:19) [MSC v.1310 32
bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for
more information.
 >>> from __future__ import absolute_import
  File "<stdin>", line 1
SyntaxError: future feature absolute_import is not defined

The PEP should be updated to reflect this.

Logged In: YES 
user_id=539787

This is still not implemented at least in HEAD
(http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Python/future.c?rev=2.15&view=auto
and 
http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Lib/__future__.py?rev=1.13&view=auto
).  I believe new functionality is avoided in micro (x.y.N)
releases, so the PEP probably will have to specify 2.5
instead of 2.4 as version of application.

import mechanisms and absolute and relative imports were reviewed recently.

Please verify if you still have an issue regarding this.

Thank you!