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-31.00:14:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CFC6DFCA-19DA-4292-920C-D2B57EEE857C@voidspace.org.uk>
In-reply-to <1553989738.24.0.446033953863.issue36485@roundup.psfhosted.org>
Content
> On 30 Mar 2019, at 23:48, Michael Foord <report@bugs.python.org> wrote:
> 
> 
> Michael Foord <michael@voidspace.org.uk> added the comment:
> 
> 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. 

* exposes (not progress)
* tested  (not treated)

Sorry. 
> 
> They're are probably some problematic caches still within unittest however. Do test results still keep alive all tracebacks until test reporting?
> 
> ----------
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue36485>
> _______________________________________
History
Date User Action Args
2019-03-31 00:14:58michael.foordsetrecipients: + michael.foord, brett.cannon, rhettinger, ezio.melotti, serhiy.storchaka
2019-03-31 00:14:58michael.foordlinkissue36485 messages
2019-03-31 00:14:57michael.foordcreate