This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.smith
Recipients crwilcox, eric.smith, jitterman, zach.ware
Date 2020-02-11.22:03:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581458637.56.0.0407723123565.issue39601@roundup.psfhosted.org>
In-reply-to
Content
But you can't just change it without breaking the code of anyone who's relying on the current behavior. If we could say "no one relies on that", that's would let us move forward with such a breaking change. But I don't think we can make that determination. And we're generally conservative with such breaking changes.

I think the current behavior doesn't make much sense, although I haven't completely analyzed the issue.
History
Date User Action Args
2020-02-11 22:03:58eric.smithsetrecipients: + eric.smith, zach.ware, jitterman, crwilcox
2020-02-11 22:03:57eric.smithsetmessageid: <1581458637.56.0.0407723123565.issue39601@roundup.psfhosted.org>
2020-02-11 22:03:57eric.smithlinkissue39601 messages
2020-02-11 22:03:57eric.smithcreate