Terry J. Reedy <tjre...@udel.edu> added the comment:

This issue was really two issues: fix doc of existing behavior; change behavior 
(which would be an enhancement).  The first has been done; the second not.  I 
think this should be closed and if anyone still proposes the second, open a new 
enhancement issue for 3.11, referencing this one, that clearly lays out the 
proposed change and rationale, given the 3.10 status quo.  (I have no opinion 
about the proposed change.)

Once someone submits a patch, we are free to change it before or after applying 
it.  But before, we give the author first crack and wait a week or so for an 
answer.

Hynek, do you still propose the change in your second patch?  If so, do you 
want to update it and make a PR?

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue13498>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to