Message 79709 - 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	gregory.p.smith
Recipients	ajaksu2, amaury.forgeotdarc, arigo, benjamin.peterson, donmez, gideon, gregory.p.smith, jcea, rhettinger, terry.reedy, vstinner
Date	2009-01-13.00:00:24
SpamBayes Score	0.09744945
Marked as misclassified	No
Message-id	<1231804825.98.0.475573740842.issue3720@psf.upfronthosting.co.za>
In-reply-to

Content
Any crash is a potential security problem. This needs to be fixed in 2.6.x without breaking 2.6.0 extension compatibility. (requiring extensions to be recompiled to fix the problem for an extension is fine, but they still need to load and work normally even if they have not been) As trunk r68560 can't be backported? what will? Is there an appropriate pre-existing hackish substitute for PyObj_NextNotImplemented or will it require adding a test anytime the tp_nextiter slot is used?

Any crash is a potential security problem.

This needs to be fixed in 2.6.x without breaking 2.6.0 extension 
compatibility.  (requiring extensions to be recompiled to fix the 
problem for an extension is fine, but they still need to load and work 
normally even if they have not been)

As trunk r68560 can't be backported?  what will?  Is there an 
appropriate pre-existing hackish substitute for PyObj_NextNotImplemented 
or will it require adding a test anytime the tp_nextiter slot is used?

History
Date	User	Action	Args
2009-01-13 00:00:26	gregory.p.smith	set	recipients: + gregory.p.smith, arigo, rhettinger, terry.reedy, jcea, amaury.forgeotdarc, vstinner, ajaksu2, donmez, benjamin.peterson, gideon
2009-01-13 00:00:25	gregory.p.smith	set	messageid: <1231804825.98.0.475573740842.issue3720@psf.upfronthosting.co.za>
2009-01-13 00:00:25	gregory.p.smith	link	issue3720 messages
2009-01-13 00:00:24	gregory.p.smith	create