Message 56943 - 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	gvanrossum
Recipients	christian.heimes, gvanrossum
Date	2007-10-30.00:29:35
SpamBayes Score	0.08598041
Marked as misclassified	No
Message-id	<1193704176.56.0.899417191845.issue1352@psf.upfronthosting.co.za>
In-reply-to

Content
Good idea. Are there any places where PyBytes or PyString are written to stderr? Or can you get away with just supporting PyUnicode? It's "dumb", not "dump". I wouldn't explicitly remove the old stderr printer -- it will be deleted automatically by the PyDict_SetItemString() call in PySys_SetObject(). That way you'll still have it when the PyFile_FromFd() call fails... This patch doesn't commute with your 'closefd' patch...

Good idea.

Are there any places where PyBytes or PyString are written to stderr? 
Or can you get away with just supporting PyUnicode?

It's "dumb", not "dump".

I wouldn't explicitly remove the old stderr printer -- it will be
deleted automatically by the PyDict_SetItemString() call in
PySys_SetObject().  That way you'll still have it when the
PyFile_FromFd() call fails...

This patch doesn't commute with your 'closefd' patch...

History
Date	User	Action	Args
2007-10-30 00:29:36	gvanrossum	set	spambayes_score: 0.0859804 -> 0.08598041 recipients: + gvanrossum, christian.heimes
2007-10-30 00:29:36	gvanrossum	set	spambayes_score: 0.0859804 -> 0.0859804 messageid: <1193704176.56.0.899417191845.issue1352@psf.upfronthosting.co.za>
2007-10-30 00:29:36	gvanrossum	link	issue1352 messages
2007-10-30 00:29:35	gvanrossum	create