Message 157856 - 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	Mark.Shannon
Recipients	Jim.Jewett, Mark.Shannon, amaury.forgeotdarc, benjamin.peterson, jcea, ncoghlan, pitrou, ron_adam, scoder
Date	2012-04-09.15:56:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1333987017.14.0.700701013169.issue13897@psf.upfronthosting.co.za>
In-reply-to

Content
3rd party code should not be accessing fields in the threadstate object, but without the accessors proposed in issue 14098 there may be no alternative. Once the patch for issue 14098 has been applied it, would it then be acceptable to remove the surperfluous fields from the frameobject? The logic for accessing sys.exc_info can be moved to into the new accessor fucntions.

3rd party code should not be accessing fields in the threadstate object,
but without the accessors proposed in issue 14098 there may be no alternative.

Once the patch for issue 14098 has been applied it, would it then be acceptable to remove the surperfluous fields from the frameobject?
The logic for accessing sys.exc_info can be moved to into the new 
accessor fucntions.

History
Date	User	Action	Args
2012-04-09 15:56:57	Mark.Shannon	set	recipients: + Mark.Shannon, jcea, amaury.forgeotdarc, ncoghlan, pitrou, scoder, ron_adam, benjamin.peterson, Jim.Jewett
2012-04-09 15:56:57	Mark.Shannon	set	messageid: <1333987017.14.0.700701013169.issue13897@psf.upfronthosting.co.za>
2012-04-09 15:56:56	Mark.Shannon	link	issue13897 messages
2012-04-09 15:56:56	Mark.Shannon	create