search

mk-fg / pretty-yaml

PyYAML-based module to produce a bit more pretty and readable YAML-serialized data
Do What The F*ck You Want To Public License
135 stars 29 forks source link

Fix ascii codec can't decode byte 0xd0 in position 2279 #5

Closed davidfischer-ch closed 10 years ago

davidfischer-ch commented 10 years ago

Downloading/unpacking pyaml (from pytoolbox->-r /home/famille/souvenirs_test/server/requirements.txt (line 18)) Downloading pyaml-13.12.0.tar.gz Running setup.py (path:/tmp/pip_build_famille/pyaml/setup.py) egg_info for package pyaml Traceback (most recent call last): File "", line 17, in File "/tmp/pip_build_famille/pyaml/setup.py", line 9, in try: readme = open(os.path.join(pkg_root, 'README.txt')).read() File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 2279: ordinal not in range(128) Complete output from command python setup.py egg_info: Traceback (most recent call last):

File "", line 17, in

File "/tmp/pip_build_famille/pyaml/setup.py", line 9, in 

try: readme = open(os.path.join(pkg_root, 'README.txt')).read()

File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode

return codecs.ascii_decode(input, self.errors)[0]

UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 2279: ordinal not in range(128)

mk-fg commented 10 years ago

I've noticed that you seem to be installing the module on python-3.3, which I'm not sure it'll even work with - only used it with python-2.X. Won't hurt fixing setup.py to work there too though, thanks.

davidfischer-ch commented 10 years ago

If you are interested in the migration topic ...

Read the setup script of pytoolbox, it uses 2to3 to convert the code to Python 3 if required !

Also use it yourself (with 2to3 -w path_to_pretty_yaml/) and check the diff, it there are actually not a lot of modifications!

You may use Travis CI (see .travis.yml) to check if it does work!

mk-fg commented 10 years ago

Yeah, guess I'll need tests for that, but will probably go with six "same code for both versions" approach - seem to be way easier to maintain than guessing what 2to3 will produce. Not using python3 anywhere though, so that will probably have to wait, maybe until 2.8 ;)