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 lopgok
Recipients benjamin.peterson, eric.araujo, georg.brandl, lopgok, nadeem.vawda, r.david.murray, rhettinger
Date 2011-06-06.20:17:35
SpamBayes Score 3.1572743e-06
Marked as misclassified No
Message-id <1307391456.64.0.628906422109.issue11802@psf.upfronthosting.co.za>
In-reply-to
Content
There are many possible solutions to this problem.
Personally, I think mine is the simplest, though it changes the API.

However, there have been several suggestions on simple fixes that don't change the API, all of which fix the resource leak.

Doing nothing will not fix the resource leak.

How about a simple fix right now, using a lru cache, fixing all versions of Python, and perhaps come up with a superior solution at a later date?
History
Date User Action Args
2011-06-06 20:17:36lopgoksetrecipients: + lopgok, georg.brandl, rhettinger, nadeem.vawda, benjamin.peterson, eric.araujo, r.david.murray
2011-06-06 20:17:36lopgoksetmessageid: <1307391456.64.0.628906422109.issue11802@psf.upfronthosting.co.za>
2011-06-06 20:17:36lopgoklinkissue11802 messages
2011-06-06 20:17:36lopgokcreate