New submission from Zooko O'Whielacronx <zooko@zooko.com>: A user of Tahoe-LAFS encountered an error in which pyOpenSSL emitted: exceptions.UnicodeDecodeError: 'utf8' codec can't decode bytes in position 0-5: unsupported Unicode code range It took some effort on the part of the user and the Tahoe-LAFS devs to delve into the code and figure out how an invalid string got into a certificate inside pyOpenSSL. Eventually the user (David Abrahams) figured out that the issue was this one: http://markmail.org/message/bla5vrwlv3kn3n7e He had installed a pyOpenSSL egg which had been built with UCS4, but his Python interpreter was UCS2. According to the thread linked above, the best way to fix this is for distutils get_platform() to include the unicode variant in its output, and then for setuptools to test the compatibility of that field when choosing an egg. Is that right? What's the next step? ---------- messages: 302 nosy: zooko priority: bug status: unread title: egg platform names don't reflect unicode variant (UCS2, UCS4) _______________________________________________ Setuptools tracker <setuptools@bugs.python.org> <http://bugs.python.org/setuptools/issue78> _______________________________________________