Message 132000 - 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	pitrou
Recipients	Arfrever, Trundle, dmalcolm, lemburg, pitrou, scott.dial, vstinner
Date	2011-03-24.16:21:41
SpamBayes Score	4.546111e-08
Marked as misclassified	No
Message-id	<1300983699.3957.6.camel@localhost.localdomain>
In-reply-to	<1300983111.45.0.212901632412.issue11393@psf.upfronthosting.co.za>

Content
> Antoine Pitrou wrote: > > It would be nice if it were enabled by default for fatal errors (and asserts perhaps?). > > I feel like a broken record. This code hardcodes fd=2 as a write target on crash, For fatal errors, you needn't be async-safe, so the fatal error code could read fileno(stderr) and give it to the traceback printing code. What do you think, Victor?

> Antoine Pitrou wrote:
> > It would be nice if it were enabled by default for fatal errors (and asserts perhaps?).
> 
> I feel like a broken record. This code hardcodes fd=2 as a write target on crash,

For fatal errors, you needn't be async-safe, so the fatal error code
could read fileno(stderr) and give it to the traceback printing code.
What do you think, Victor?

History
Date	User	Action	Args
2011-03-24 16:21:44	pitrou	set	recipients: + pitrou, lemburg, scott.dial, vstinner, Arfrever, Trundle, dmalcolm
2011-03-24 16:21:41	pitrou	link	issue11393 messages
2011-03-24 16:21:41	pitrou	create