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

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

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

• Previous message (by thread): [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
• Next message (by thread): [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

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

• Previous message (by thread): [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
• Next message (by thread): [Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4