Re: [Python-Dev] Code quality report

2016-09-24 Thread Guido van Rossum
Thanks for watching our back, Christian! Regarding the security bugs, what would be most helpful? Code reviews? Patches? Testing? Just commits? Hopefully there are some people here who want to help making Python 3.6 more secure (I hear this list has thousands of lurkers :-). On Sat, Sep 24, 2016 a

[Python-Dev] Code quality report

2016-09-24 Thread Christian Heimes
Hi, here is a short code quality report. Overall we are in a good shape for Python 3.6.0. I'm a bit worried about the amount of security bugs, though. Some haven't progressed in more than a year. Coverity Scan - 3.6.0b1 added a bunch of new defects, most of them were false positives

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

2016-09-24 Thread Benjamin Peterson
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 : > > > > Just dump the compat macros in Python 4.0 I think.

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

2016-09-24 Thread Benjamin Peterson
On Fri, Sep 23, 2016, at 00:04, Victor Stinner wrote: > 2016-09-23 8:47 GMT+02:00 Benjamin Peterson : > > 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 wit