Re: [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
2016-09-22 8:02 GMT+02:00 Benjamin Peterson : > 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. Note: The Gtk project has similar questions on backward compatibility ;-) https://blogs.gnome.org/desrt/2016/06/13/gtk-4-0-is-not-gtk-4/ (Migration to Gtk3 was also painful for developers, no?) Victor ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
On Thu, Sep 22, 2016, at 04:44, Victor Stinner wrote: > 2016-09-22 8:02 GMT+02:00 Benjamin Peterson : > > 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. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
