On 9/9/05, Michael Chermside <[EMAIL PROTECTED]> wrote: > I think it would > provide a REALLY nice migration path if it were possible to write > Python 3.0 code in Python 2.x (for large values of x) so long as you > included an appropriate preamble of "from __future__ import" statements.
Perhaps I was not clear, but that was the reason of my proposal. I agree it is not necesary, but this will help developers to transition from Py2.X to Py3.0 in a consistent way. I will vote +1 for any attemps to populate __future__ module if that enables writing working Py3K code as soon as possible in Py2.X .. > I love making Perl users jealous, So I love! ;) -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ 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
