Over a million developers have joined DZone.

Mollified About ResourceWarnings

DZone's Guide to

Mollified About ResourceWarnings

Free Resource

Prove impact and reduce risk when rolling out new features. Optimizely Full Stack helps you experiment in any application.

Last month I griped about ResourceWarnings in Python 3, arguing they’re a useless irritation in a language that can clean up resources automatically. Python core developer Nick Coghlan responded in the comments and I understand the choice now.

Nick explains that ResourceWarnings reveal problems that would make the Python standard library inefficient running in PyPy. A resource like a socket can clean itself up promptly in CPython, but now that it issues a ResourceWarning when it isn’t explicitly closed, the socket helps library authors prepare for PyPy, in which resources are not promptly cleaned up. If I decide that lazy cleanup is ok, I can avoid ResourceWarnings by using a weakref callback to close the resource before it’s deleted, whenever that happens.

Nick also pointed out that ResourceWarnings are off by default in normal Python programs—I just saw them all the time because I usually run my code in nosetest.

Read our full discussion in the comments.

Props to Nick for taking the time to explain.

With SDKs for all major client and server side platforms, you can experiment on any platform with Optimizely Full Stack.


Published at DZone with permission of A. Jesse Jiryu Davis, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}