> The csv module says it's not unicode safe but the 2.5 docs [3] have a
> workaround for this. While the workaround says nothing about
> sys.setdefaultencoding() it simply does not work with the default
> encoding, "ascii." Is this _the_ problem with the csv module? Should
> I give up and use XM
I'm seeing conflicting opinions on whether to put
sys.setdefaultencoding('utf-8') in sitecustomize.py or not ([1] vs.
[2]) and frankly I'm confused.
The csv module says it's not unicode safe but the 2.5 docs [3] have a
workaround for this. While the workaround says nothing about
sys.setdefaultenc
