On 2/10/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: > On Fri, Feb 10, 2006 at 11:06:24PM +0100, M.-A. Lemburg wrote: > > Guido van Rossum wrote: > > >> PEP 328: Absolute/Relative Imports > > > > > > Yes, please. > > > +0 for adding relative imports. -1 for raising errors for > > in-package relative imports using the current notation > > in Python 2.6. > > +1/-1 for me. Being able to explicitly demand relative imports is good, > breaking things soon bad. I'll happily shoehorn this in at the sprints after > PyCon ;)
The PEP has the following timeline (my interpretation): 2.4: implement new behavior with from __future__ import absolute_import 2.5: deprecate old-style relative import unless future statement present 2.6: disable old-style relative import, future statement no longer necessary Since it wasn't implemented in 2.4, I think all these should be bumped by one release. Aahz, since you own the PEP, can you do that (and make any other updates that might result)? -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
