[Python-Dev] cpython (3.6): replace usage of Py_VA_COPY with the (C99) standard va_copy (original) (raw)
Benjamin Peterson benjamin at python.org
Sat Sep 24 04:10:26 EDT 2016
- 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 ]
On Fri, Sep 23, 2016, at 00:04, Victor Stinner wrote:
2016-09-23 8:47 GMT+02:00 Benjamin Peterson <benjamin at python.org>: > I'm being flippant here because of the triviality of the change. Anyone > using PyVACOPY or PyMEMCPY can fix their code in a backwards and > forwards compatible manner in 7 seconds with a sed command.
Python 3 had the same argument with 2to3: run 2to3 once, and you are done. C99 is a new thing for Python >= 3.6, but when you want to support Python 2.7 and 3.5, you are stuck at Visual Studio 2010 which is less happy with C99 than VS 2015...
Python 2.7 doesn't provide Py_VA_COPY, so using it wouldn't do you much good anyway in term of Python 2/3 compatibility.
This is not like 2to3 because the automatic transform is correct in all cases.
- 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 ]