➜

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 db3l
Recipients EWDurbin, db3l, pablogsal, vstinner, zach.ware
Date 2020-11-27.20:52:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1606510379.52.0.499071585457.issue41701@roundup.psfhosted.org>
In-reply-to
Content 
I was wondering if there was any update on whether or not this new behavior can be corrected?

I was attempting to review a buildbot failure today and it's actually pretty tough to "race the refresh" when trying to review the build steps and logs.
History
Date User Action Args
2020-11-27 20:52:59db3lsetrecipients: + db3l, vstinner, zach.ware, EWDurbin, pablogsal
2020-11-27 20:52:59db3lsetmessageid: <1606510379.52.0.499071585457.issue41701@roundup.psfhosted.org>
2020-11-27 20:52:59db3llinkissue41701 messages
2020-11-27 20:52:59db3lcreate