Python 3.2 has some deadly infection
Steven D'Aprano <steve+comp.lang.python at pearwood.info>:
>> "Can be replaced" by who? By the Python developers? By me? By random
>> library calls?
> By you. sys.stdout and friends are writable. Any code you call may
> have replaced them with another file-like object, and you should
> honour that.
I can of course overwrite even sys and os and open and all. That hardly
merits mentioning in the API documentation.
What I'm afraid of is that the Python developers are reserving the right
to remove the buffer and detach attributes from the standard streams in
a future version. That would be terrible.
If it means some other module is allowed to commandeer the standard
streams, that would be bad as well.
Worst of all, I don't know why the caveat had to be there.
Or is it maybe because some python command line options could cause
buffer and detach not to be there? That would explain the caveat, but
still would be kinda sucky.