Message 59698 - Python tracker

➜

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	hniksic
Recipients	christian.heimes, gvanrossum, hniksic
Date	2008-01-11.08:46:39
SpamBayes Score	0.23200646
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
I agree that a leak would very rarely occur in practice, but since there is a straightforward fix, why not apply it? If nothing else, the code in the core should be an example of writing leak-free Python/C code, and a fix will also prevent others from wasting time on this in the future.

I agree that a leak would very rarely occur in practice, but since there
is a straightforward fix, why not apply it?  If nothing else, the code
in the core should be an example of writing leak-free Python/C code, and
a fix will also prevent others from wasting time on this in the future.

History
Date	User	Action	Args
2008-01-11 08:46:41	hniksic	set	spambayes_score: 0.232006 -> 0.23200646 recipients: + hniksic, gvanrossum, christian.heimes
2008-01-11 08:46:41	hniksic	set	spambayes_score: 0.232006 -> 0.232006 messageid: <[email protected]>
2008-01-11 08:46:39	hniksic	link	issue1782 messages
2008-01-11 08:46:39	hniksic	create