Jonathan Bastien-Filiatrault <j...@zerospam.ca> added the comment:
> But it will still "leak" when you display ResourceWarning warnings with an
> action different than "always". In this case, IMHO the root issue is more the
> code which doesn't clo
Jonathan Bastien-Filiatrault <j...@zerospam.ca> added the comment:
@vstinner Yes, from what I saw, the leak was from the registry / deduplication
logic.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Jonathan Bastien-Filiatrault <j...@zerospam.ca> added the comment:
We just got hit by this. We had one specific case where files with unique names
were not being closed and Python was leaking a lot of memory over a few days.
--
nosy: +Jonathan Bastien-Filia
