[Python-Dev] Common subset of python 2 and python 3

Nachshon David Armon nachshon.armon at gmail.com
Sun Jan 12 18:39:55 CET 2014

On Sun, Jan 12, 2014 at 3:58 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 12 Jan 2014 23:39, "Nachshon David Armon" <nachshon.armon at gmail.com>
> wrote:

>> I propose that this new version of python use the python 3 unicode model.
>> As the version of python will be fully compatible with both python 2 and
>> with python 3 but NOT necsesarily with all existing code in either. It is
>> designed as a porting tool only.
> Ah, I missed this on the first read through - that combination of
> requirements doesn't quite make sense (the text models are fundamentally
> incompatible in a way that forces developers to resolve ambiguities that
> Python 2 would silently tolerate until it hit a bad combination of input
> data).

 while that is true, it is possible to program unicode correctly in
python 2 while remaining compatible with python 3. (a combination of
"from future import unicode_literal" and properly using the encode and
decode functions.). I would prefer a stripped version of python 3 that
does not support anything that will really conflict with python 2. for
porting purposes only of course. my employer still uses python 2 so
the idea is to force other developers to use something that will force
working on both during the transition without every single one having
to be extra careful to support both versions.

More information about the Python-Dev mailing list