➜

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 michael.foord
Recipients brett.cannon, ezio.melotti, michael.foord, rhettinger, serhiy.storchaka
Date 2019-03-30.23:48:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553989738.24.0.446033953863.issue36485@roundup.psfhosted.org>
In-reply-to
Content 
An auto-magic cache clearing mechanism is really tempting. I tend to agree with Raymond though, if code needs and progress a cache clearing mechanism it should be treated and accessible. 

They're are probably some problematic caches still within unittest however. Do test results still keep alive all tracebacks until test reporting?
History
Date User Action Args
2019-03-30 23:48:58michael.foordsetrecipients: + michael.foord, brett.cannon, rhettinger, ezio.melotti, serhiy.storchaka
2019-03-30 23:48:58michael.foordsetmessageid: <1553989738.24.0.446033953863.issue36485@roundup.psfhosted.org>
2019-03-30 23:48:58michael.foordlinkissue36485 messages
2019-03-30 23:48:58michael.foordcreate