Re:Setting The Default Encoding In Python
by joeyespo on Thursday June 13, 2013 @01:00PM
(#5875141)
Ah, didn't realize it was a year old. I was just going through your blog and thought this was interesting! Agreed, changing global state is bad. This is an exceptional thing to do.
Especially inside of a python module intended to be imported by others.
There's a very good reason why the defaultencoding is removed from the Python namespace and you have to resort to hackery to access it.
You should be handling encode/decode explicitly; not resorting to changing the default system encoding. You will break other consumers.As the other poster said, just move to Python 3 and stop worrying about this mess.
Or you could use Python 3 and stop worrying.
[1] http://www.python.org/dev/peps/pep-0263/
I agree that setting global state is a bad idea. However, client satisfaction is more important than a temporary hack.