Flavian Hautbois added the comment:
So what do we do about this?
Two possibilities:
1. We merge PR 9765 and close PRs 345 and 201, as 9765 seems more
straighforward and was already approved. 9765 should be resubmitted to be
merged since the base repo does not exist anymore, I could do that
Change by Flavian Hautbois :
--
keywords: +patch
pull_requests: +14746
pull_request: https://github.com/python/cpython/pull/14977
___
Python tracker
<https://bugs.python.org/issue30
Change by Flavian Hautbois :
--
keywords: +patch
pull_requests: +14745
pull_request: https://github.com/python/cpython/pull/14976
___
Python tracker
<https://bugs.python.org/issue29
Change by Flavian Hautbois :
--
keywords: +patch
pull_requests: +14739
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/14970
___
Python tracker
<https://bugs.python.org/issu
Change by Flavian Hautbois :
--
keywords: +patch
pull_requests: +14653
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/14864
___
Python tracker
<https://bugs.python.org/issu
Flavian Hautbois added the comment:
Are you going to open a PR for this patch? I think that would be a nice addition
--
nosy: +flavianhautbois
___
Python tracker
<https://bugs.python.org/issue27