[tahoe-dev] [tahoe-lafs] #704: eggs don't say whether they have UCS2 or UCS4 unicode implementation
tahoe-lafs
trac at allmydata.org
Mon Sep 21 19:33:41 PDT 2009
#704: eggs don't say whether they have UCS2 or UCS4 unicode implementation
---------------------------+------------------------------------------------
Reporter: bewst | Owner: bewst
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: packaging | Version: 1.4.1
Resolution: | Keywords:
Launchpad_bug: |
---------------------------+------------------------------------------------
Changes (by zooko):
* owner: zooko => bewst
Comment:
There was no request for you outstanding, so this should have been
unassigned from you. However, just recently I started a discussion on the
python-dev list, and referenced this ticket, and they said that the
symptoms that we observed are not the symptoms they would expect from
having an inconsistency of internal unicode format between Python
interpreter and Python module. If that were the problem, we should have
seen something like "undefined symbol:
PyUnicodeUCS4_FromUnicode", not the utf-8 decode error that we saw.
Here is the comment on python-dev to that effect:
http://mail.python.org/pipermail/python-dev/2009-September/091943.html
So, now there ''is'' something you could do to help: see if you still have
that pyOpenSSL library that you mentioned, the removal of which fixed this
problem for you, so we can try to see what was wrong with it.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/704#comment:17>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list