On Fri, Sep 23, 2016, at 09:32, Steven D'Aprano wrote: > On Thu, Sep 22, 2016 at 11:47:20PM -0700, Benjamin Peterson wrote: > > > > On Thu, Sep 22, 2016, at 04:44, Victor Stinner wrote: > > > 2016-09-22 8:02 GMT+02:00 Benjamin Peterson <benja...@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. > > Sorry, I haven't been following this thread in detail, so perhaps I've > misunderstood. Are you assuming that anyone who is building Python from > source is automatically able to diagnose C level build failures and > known how to fix them using sed?
I am assuming authors of CPython extensions possess those skills. _______________________________________________ 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
