Marc-Andre Lemburg added the comment:

On 06.09.2014 21:14, Nick Coghlan wrote:
> This investigation also showed why the original tests that used a
> non-unique name didn't work: the codec was getting cached the first time
> through and hence not seeing the different codecs registered by other tests.
> MAL, my plan was to provide an API to forget a specific named codec rather
> than flush the whole cache. I agree a private C API would also be a good
> idea, though.

I don't think such a specific API for only forgetting a single codec
is useful outside this particular test case, since you typically
don't know the names of the cached codecs.


Python tracker <>
Python-bugs-list mailing list

Reply via email to