C99 has shown slow adoption by microsoft compilers on windows. On this
platform, the support of va_copy() is recent and started with Visual Studio
2013. Therefore, starting from Python 3.5, PY_VA_COPY can now be mapped
directly to the native implementation of va_copy(). Hence, the proposed
change might be justified.
On Wed, Sep 21, 2016 at 12:42pm, Victor Stinner < victor.stin...@gmail.com
[victor.stin...@gmail.com] > wrote:
I see that the old macro is now an alias to va_copy(). A similar change was
done for Py_MEMCPY(). Would it make sense to put these old macros in a new
backward_compat.h header, so maybe one day we can remove them? :-)
Maybe we need at least a comment mentionning when (python version) the
macro became an alias.
Python-Dev mailing list