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 ggenellina
Recipients ggenellina, pitrou, steven.daprano
Date 2009-01-15.04:53:09
SpamBayes Score 0.00797282
Marked as misclassified No
Message-id <>
> It probably uses sys.getdefaultencoding() instead.

That would be wrong too, according to the cited documentation.

file.encoding is a read only attribute; it can be set in C code using 
PyFile_SetEncoding. Apart from its definition in fileobject.c, it is 
*only* used by PyInitialize when sys.stdin/stdout/stderr are created. 
There are no tests, nor any other use of it anywhere. Apparently the 
attribute *is* checked when writing unicode objects, but it does not 

I'm guessing now, but probably the original intent was to make file 
objects behave like the wrapper returned by works now -- 
later it was deemed impractical and forgotten. Now, the "declarative" 
meaning of file.encoding survives, but the "behavior" is broken.

I don't know what would be the right thing to do. The encoding used by 
stdin/stdout/stderr is valuable information so the attribute should 
remain. Fixing the behavior is like having a crippled 
StreamReaderWriter and I don't see the point. But StreamReaderWriter 
has an "encoding" attribute too, and it "works", so one cannot rely on 
having such attribute to know whether the stream automatically encodes 
its data or not.
Date User Action Args
2009-01-15 04:53:13ggenellinasetrecipients: + ggenellina, pitrou, steven.daprano
2009-01-15 04:53:13ggenellinasetmessageid: <>
2009-01-15 04:53:12ggenellinalinkissue4947 messages
2009-01-15 04:53:10ggenellinacreate