Fixed in upstream master branch with commit

commit b67980d334078df54a78f354c5d207a5ee9a267b
Author: Matt Domsch <>
Date:   Mon Apr 7 22:48:14 2014 -0500

    better MIME magic library handling
    The different mime magic libraries expect input to their from_file(),
    file(), and id_filename() functions, respectively, to take either a
    filesystem-encoded (generally UTF-8) string, or a unicode filename.
    Different versions of the libraries each expect different inputs for
    filename though.  This is annoying.
    Here, we call these functions, first with a UTF-8 encoded string
    filename.  If that fails with a UnicodeDecodeError, we try again
    passing a unicode filename.
    Also, delete mime_magic_buffer() everywhere, and the introspection of
    gzip files to see what type of object is inside.  It doesn't matter to
    the S3 web server - it needs to be type application/x-gzip, not
    type=application/tar encoding=gzip (as mimetypes would tell us). We
    stopped using the encoding value here as HTTP Content-Encoding in
    commit 44e35899a anyhow.

On Thu, May 8, 2014 at 6:33 AM, Jamshid Karimi <> wrote:
Problem: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33: ordinal not in range(128)
S3cmd:   1.1.0-beta3

Traceback (most recent call last):
  File "/usr/bin/s3cmd", line 1800, in <module>
  File "/usr/bin/s3cmd", line 1741, in main
  File "/usr/bin/s3cmd", line 965, in cmd_sync
    return cmd_sync_local2remote(args)
  File "/usr/bin/s3cmd", line 922, in cmd_sync_local2remote
    response = s3.object_put(src, uri, extra_headers, extra_label = seq_label)
  File "/usr/share/s3cmd/S3/", line 363, in object_put
    content_type = mime_magic(filename)
  File "/usr/share/s3cmd/S3/", line 43, in mime_magic
    return magic_.file(file)
  File "/usr/lib/python2.7/dist-packages/", line 125, in file
    return _file(self._magic_t, filename.encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33: ordinal not in range(128)

Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now