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 meador.inge
Recipients Suman.Saha, ezio.melotti, meador.inge
Date 2011-09-22.02:52:35
SpamBayes Score 0.000621196
Marked as misclassified No
Message-id <1316659956.46.0.328480063182.issue13020@psf.upfronthosting.co.za>
In-reply-to
Content
In general I agree that a test case is needed, but in this particular
case its looks to be non-trivial to come up with one.  The only way
the reference leak is triggered is when memory is exhausted during an
attempt to new up a 'PyStructSequence' object.
History
Date User Action Args
2011-09-22 02:52:36meador.ingesetrecipients: + meador.inge, ezio.melotti, Suman.Saha
2011-09-22 02:52:36meador.ingesetmessageid: <1316659956.46.0.328480063182.issue13020@psf.upfronthosting.co.za>
2011-09-22 02:52:35meador.ingelinkissue13020 messages
2011-09-22 02:52:35meador.ingecreate