RetroSearch Browse

Fri Sep 23 03:03:20 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-September/146534.html

On Fri, Sep 23, 2016 at 4:47 PM, Benjamin Peterson <benjamin at python.org> wrote:
> On Thu, Sep 22, 2016, at 04:44, Victor Stinner wrote:
>> 2016-09-22 8:02 GMT+02:00 Benjamin Peterson <benjamin at python.org>:
>> > Just dump the compat macros in Python 4.0 I think.
>>
>> Please don't. Python 3 was so painful because we decided to make
>> millions of tiny backward incompatible changes. To have a smooth
>> Python 4.0 release, we should only remove things which were already
>> deprecated since at least 2 cycles, and well documented as deprecated.
>
> I'm being flippant here because of the triviality of the change. Anyone
> using Py_VA_COPY or Py_MEMCPY can fix their code in a backwards and
> forwards compatible manner in 7 seconds with a sed command.

In fact, this kind of thing would be perfect for Python 4.0 - it's
technically backward incompatible (thus justifying the 4.0 number),
but removes only things that have been deprecated for some time, and
have simple and direct translations.

ChrisA

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

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

[Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy