[Python-Dev] Question - Bug Triage for 3.4 & 3.5

Steve Dower steve.dower at python.org
Wed Feb 20 10:22:11 EST 2019

On 20Feb.2019 0711, Stephane Wirtel wrote:
> After discussion with Victor, my proposal will generate noise with the
> ML, maybe for nothing.
> On 02/20, Stephane Wirtel wrote:
>> Hi,
>> As you know, Python 3.4 and 3.5 are in security mode and the EOL for
>> these versions are respectively 2019-03-16 and 2020-09-13.
>> Number of issues
>> 3.4: 1530 issues
>> 3.5: 1901 issues
>> But some issues are not related to the security.
>> Could we update these issues (non-security) to 3.6/3.7 & 3.8?
>> Cheers,
>> Stéphane

It'll make same noise, sure, but if we schedule a bulk close of issues
that have not been touched since 3.6 was released then at least it'll be
easy to "mark all as read". And searching for current issues will become

I'm always in favor of cleaning up inactionable bugs (as much as I'm in
favor of keeping actionable-but-low-priority bugs open, which causes
quite a few conflicts at work...)

That said, maybe it makes sense to wait until 2.7's EOL and do them all
at once?


More information about the Python-Dev mailing list