RetroSearch Browse

Fri Sep 9 23:38:18 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-September/056352.html

On 9/9/05, Michael Chermside <mcherm at mcherm.com> 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

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/056352.html below:

[Python-Dev] PEP 3000 and new style classes