[Python-Dev] Proposal: new environment variable PYTHONSTDOUTENCODING (original) (raw)
M.-A. Lemburg mal at egenix.com
Tue May 20 22:15:48 CEST 2008
- Previous message: [Python-Dev] Proposal: new environment variable PYTHONSTDOUTENCODING
- Next message: [Python-Dev] Proposal: new environment variable PYTHONSTDOUTENCODING
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2008-05-20 21:34, Martin v. Löwis wrote:
I'm not exactly sure why, since using .encoding would be useful in all cases. Right, I think it should use the file's encoding also for .write.
Could you add that to the proposal ?!
Please also add the ability to set the .encoding on file objects.
This would make adjusting e.g. sys.stdout.encoding easier from within Python.
Thanks,
Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, May 20 2008)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611- Previous message: [Python-Dev] Proposal: new environment variable PYTHONSTDOUTENCODING
- Next message: [Python-Dev] Proposal: new environment variable PYTHONSTDOUTENCODING
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]