➜

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 levkivskyi
Recipients gvanrossum, josh.r, levkivskyi, ned.deily, python-dev, serhiy.storchaka, yselivanov
Date 2016-11-10.16:45:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1478796307.94.0.473065636226.issue28649@psf.upfronthosting.co.za>
In-reply-to
Content 
I think tearDown() is not necessary. But on the other hand it could be nice to have a method in tests to force cache clear. I would propose it not as a default, but as an opt-in to check that cache works well, or that a certain tested feature is "cache independent", etc.
History
Date User Action Args
2016-11-10 16:45:07levkivskyisetrecipients: + levkivskyi, gvanrossum, ned.deily, python-dev, serhiy.storchaka, yselivanov, josh.r
2016-11-10 16:45:07levkivskyisetmessageid: <1478796307.94.0.473065636226.issue28649@psf.upfronthosting.co.za>
2016-11-10 16:45:07levkivskyilinkissue28649 messages
2016-11-10 16:45:07levkivskyicreate