As specifically to the flaws in our workflow and the backlog, this is exactly what the Developer-in-Residence program was designed to address:
https://pyfound.blogspot.com/2021/04/the-psf-is-hiring-developer-in.html Stay tuned! -Barry > On Jun 29, 2021, at 09:56, Joannah Nanjekye <nanjekyejoan...@gmail.com> wrote: > > > why doesn't it get merged? > > The last significant discussion from a core dev on the most relevant PR here: > https://github.com/python/cpython/pull/4819 > shows that Antoine was familiarizing himself with the feature and had added > it to their to do list. > > Merging something is also a responsibility to whoever does it, so I suggest > we approach this with grace given at least someone > promised to look into it. > > BTW, am not writing off your concerns. > > On Tue, Jun 29, 2021 at 1:36 PM <esmeraldagar...@byom.de> wrote: > I just stumbled upon the following issue and subsequent pull request. It is a > very small bugfix. There is currently a bug in Python and this pull request > fixes it. It's not a new feature or an enhancement, it is a bugfix! Yet, it > doesn't get reviewed, nor merged. And this has been going on since March > 2017. Why not just merge this? It's not like it's huge or obstructing or > obfuscating the current code base? There's always time to write an > improvement or a complete rewrite of this module feature later for an > upcoming minor release. But if there is currently a bug in Python and the > bugfix is available - why doesn't it get merged? > > https://github.com/python/cpython/pull/4819 > > If this doesn't get fixed, doesn't that mean the Python review process is > flawed? Sure, Python is an open source project and many people just work in > their free time. But this doesn't really apply here, does it? The bugfix is > available. Only a review is required. All this is happening while new > features get added to Python with every new minor version. While the bug is > allowed to live there. Please help me understand how this can happen. > > I love Python. No hard feelings. But this is really bugging me and I can't > help but feel disappointed. > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/TTJAVTPF6RYO63GTBSTXFJG3IVCYPHXT/ > Code of Conduct: http://python.org/psf/codeofconduct/ > > > -- > Best, > Joannah Nanjekye > "You think you know when you learn, are more sure when you can write, even > more when you can teach, but certain when you can program." > Alan J. Perlis > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/BCGNYV73S2O44OJ3OT2L3HKDK3BFLAE3/ > Code of Conduct: http://python.org/psf/codeofconduct/
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/KJW4WBL27EB7EDVYDC3HL22VGXYJZ7SF/ Code of Conduct: http://python.org/psf/codeofconduct/
