RetroSearch Browse

Mon Nov 23 19:47:46 CET 2009 · https://mail.python.org/pipermail/python-dev/2009-November/094349.html

M.-A. Lemburg <mal <at> egenix.com> writes:
> 
> We could then also have a py2compat.c to hold corresponding
> C code, e.g. to provide compatibility wrappers of new APIs that
> implement different semantics in 3.x.

If the semantic differences are embodied in the builtin object types I wonder
how you can make a compatibility wrapper (short of reimplementing the 2.x
types). An int is not a long, a bytes is not a str is not a unicode.

I'm not sure concealing the differences between 2.x and 3.x behind such a
wrapper is a good idea. It would be better if people became aware of / learnt
about the new semantics.

Regards

Antoine.

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

Showing content from https://mail.python.org/pipermail/python-dev/2009-November/094349.html below:

[Python-Dev] Removal of intobject.h in 3.1