Bugs item #1157255, was opened at 2005-03-05 15:23 Message generated for change (Comment added) made by tzot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1157255&group_id=5470
Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kent Johnson (kjohnson) Assigned to: Nobody/Anonymous (nobody) Summary: PEP 328 and Python 2.4 error Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Christos Georgiou (tzot) Date: 2005-03-20 13:00 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1157255&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
