Message 56955 - 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	christian.heimes
Recipients	christian.heimes, gvanrossum
Date	2007-10-30.05:51:55
SpamBayes Score	0.010102446
Marked as misclassified	No
Message-id	<4726C676.1060906@cheimes.de>
In-reply-to	<1193704176.56.0.899417191845.issue1352@psf.upfronthosting.co.za>

Content
Guido van Rossum wrote: > Are there any places where PyBytes or PyString are written to stderr? > Or can you get away with just supporting PyUnicode? I could have simple copied the write method from _fileio.c and letting the argument parser do its job instead of fighting with the API for 20 minutes. : > It's "dumb", not "dump". I need an IDE with a context aware spell checker :] > 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... I didn't know that. I'll keep it in place.

Guido van Rossum wrote:
> Are there any places where PyBytes or PyString are written to stderr? 
> Or can you get away with just supporting PyUnicode?

I could have simple copied the write method from _fileio.c and letting
the argument parser do its job instead of fighting with the API for 20
minutes. :

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

I need an IDE with a context aware spell checker :]

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

I didn't know that. I'll keep it in place.

History
Date	User	Action	Args
2007-10-30 05:51:57	christian.heimes	set	spambayes_score: 0.0101024 -> 0.010102446 recipients: + christian.heimes, gvanrossum
2007-10-30 05:51:57	christian.heimes	link	issue1352 messages
2007-10-30 05:51:55	christian.heimes	create