2013/10/29 Nick Coghlan :
> I was thinking you could turn on warnings->errors and then catch the
> exception, and use that to get hold of the original object that
> triggered the resource warning, and then fed *that* into
> tracemalloc.get_object_traceback(). But, alas, even if we tweaked
> Resourc
On 29 October 2013 22:07, Victor Stinner wrote:
> Hi,
>
> Since Python 3.3, when a file or socket object is destroyed before
> being closed, a ResourceWarning is emitted. The warning is emitted
> where the object is destroyed: it's common to see "gc.collect()"
> location in the Python test suite f
Hi,
Since Python 3.3, when a file or socket object is destroyed before
being closed, a ResourceWarning is emitted. The warning is emitted
where the object is destroyed: it's common to see "gc.collect()"
location in the Python test suite for example.
Tarek Ziadé asked on Twitter if there is a tool
