[ Release ] Python 3.10a5 and release blockers
Hi everyone,
I am prepared to start the release process for Python 3.10 a5 but there are several issues marked as release blockers that affect 3.10:
- https://bugs.python.org/issue38302
- https://bugs.python.org/issue42634
- https://bugs.python.org/issue41490
- https://bugs.python.org/issue42967
- https://bugs.python.org/issue42899
Although release blockers mainly apply to important releases, there are two are security issues and some of the rest involve changes in bytecode or the tracing machinery, so I would prefer if these issues are addressed before making a new release as many maintainers are waiting for the next alpha to test again the bugs that they reported.
Please, if you are involved in any of these issues try to see if is possible to address them or if you think is ok to release the alpha without a fix, please, drop me an email stating so.
Thanks,
Regards from cloudy London, Pablo Galindo Salgado
Hi Pablo,
Looks like alpha 5 was scheduled for today. I am willing to take care of this issue - https://bugs.python.org/issue42967 The patch is reasonable, but the changes are backwards incompatible. Since it is with an underlying parsing library, the decision here is tricky one way or the other. I will let you know if I decide it for 3.10, an easier decision than backport. I just have to see how other libraries took care of this issue.
But if for some reason, we couldn't include in -alpha5, we should plan -alpha6.
Thanks, Senthil
On Mon, Feb 1, 2021 at 11:48 AM Pablo Galindo Salgado <pablogsal@gmail.com> wrote:
Hi everyone,
I am prepared to start the release process for Python 3.10 a5 but there are several issues marked as release blockers that affect 3.10:
- https://bugs.python.org/issue38302
- https://bugs.python.org/issue42634
- https://bugs.python.org/issue41490
- https://bugs.python.org/issue42967
- https://bugs.python.org/issue42899
Although release blockers mainly apply to important releases, there are two are security issues and some of the rest involve changes in bytecode or the tracing machinery, so I would prefer if these issues are addressed before making a new release as many maintainers are waiting for the next alpha to test again the bugs that they reported.
Please, if you are involved in any of these issues try to see if is possible to address them or if you think is ok to release the alpha without a fix, please, drop me an email stating so.
Thanks,
Regards from cloudy London, Pablo Galindo Salgado
python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/Z... Code of Conduct: https://www.python.org/psf/codeofconduct/
participants (2)
-
Pablo Galindo Salgado
-
Senthil Kumaran