This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Valentyn Tymofieiev, brett.cannon, eric.snow, nanjekyejoannah, ncoghlan, p-ganssle, pablogsal, pitrou, vstinner
Date 2020-01-15.21:27:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579123672.99.0.505666638321.issue35943@roundup.psfhosted.org>
In-reply-to
Content
> The changes required to successfully do this backport are many and affect critical areas. I am not in a hurry to do this. If anyone else wants to take this up quickly, please do.

Do you mean that there is a risk that the backport introduces a regression in another part of the code? If yes, I would suggest to not backport the change to *stable* branches.

People survived with bug. Do you really *have to* backport the fix?

Note: this issue is closed. If you consider to backport it, I suggest to reopen the issue.
History
Date User Action Args
2020-01-15 21:27:53vstinnersetrecipients: + vstinner, brett.cannon, ncoghlan, pitrou, eric.snow, p-ganssle, pablogsal, nanjekyejoannah, Valentyn Tymofieiev
2020-01-15 21:27:52vstinnersetmessageid: <1579123672.99.0.505666638321.issue35943@roundup.psfhosted.org>
2020-01-15 21:27:52vstinnerlinkissue35943 messages
2020-01-15 21:27:52vstinnercreate