Join GitHub today
content_encoding != charset, bug #153 #157
Thus spake Castedo Ellerman:
I just got bitten by this because I used a recent s3cmd to upload a
The problem is that the code you added is confounding the "charset"
The data member "self.config.encoding" of class S3 in S3.py is a
In contrast the variable "content_encoding" originally added by
It is with your merge that you incorrectly assign a charset
This patch from Castedo fixes the mistake.