Message 172283 - 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.

In-reply-to
Author	mark.dickinson
Recipients	Arfrever, asvetlov, mark.dickinson, python-dev, serhiy.storchaka, vstinner
Date	2012年10月07日.09:41:21
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1349602881.82.0.717242732017.issue16096@psf.upfronthosting.co.za>

Content
Yes, reopening issue 14700 sounds good to me. I'm not against fixing these issues in the bugfix branches, but we need to do it carefully (which unfortunately probably also means slowly). I think that for the bugfix branches, each fix should be accompanied by a test that exercises the original bug. I'd also suggest having a separate issue for each bug, for ease of review. I'd probably also prioritise those bugs that can be triggered without having huge structures in memory: e.g., the issue 14700 bug seems more important to fix than the PyTuple_New bug.

Content

Yes, reopening issue 14700 sounds good to me.
I'm not against fixing these issues in the bugfix branches, but we need to do it carefully (which unfortunately probably also means slowly). I think that for the bugfix branches, each fix should be accompanied by a test that exercises the original bug. I'd also suggest having a separate issue for each bug, for ease of review.
I'd probably also prioritise those bugs that can be triggered without having huge structures in memory: e.g., the issue 14700 bug seems more important to fix than the PyTuple_New bug.

History
Date	User	Action	Args
2012年10月07日 09:41:21	mark.dickinson	set	recipients: + mark.dickinson, vstinner, Arfrever, asvetlov, python-dev, serhiy.storchaka
2012年10月07日 09:41:21	mark.dickinson	set	messageid: <1349602881.82.0.717242732017.issue16096@psf.upfronthosting.co.za>
2012年10月07日 09:41:21	mark.dickinson	link	issue16096 messages
2012年10月07日 09:41:21	mark.dickinson	create

homepage