Irit Katriel <iritkatr...@gmail.com> added the comment:
On second thought I won't keep this open till it expires. This is a low priority bug which no longer exists in new versions because it was fixed by accident due to another change. I don't believe anyone would care enough about this to investigate how it accidentally got fixed (and then investigate how it can be fixed in 3.9). In my judgement it's not worth anyone (core devs or contributors) spending any more time on this (even just reading it and moving on). We have over 7000 open issues and only a handful of volunteers reviewing and fixing them. I found msg412785 a bit rude, but I will give you the benefit of the doubt that you didn't intend for it to come across that way. If you still believe that I am overstepping my authority and this should be decided by the RMs, I suggest you raise this with the SC or on python-dev. ---------- resolution: -> out of date status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42548> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
