Re: UnicodeDecodeError

Philipp von Weitershausen wrote:
>>>So, to get DirectoryStorage behaving the same as FileStorage we could add:
>>>
>>>   u = str(u)
>>>   d = str(d)
>>
>>
>>Syncing the behaviour is definitely a good idea; we obviously need a
>>general fix from the Zope 3 side. As said before, I will bring this up
>>among the Zope 3 developers.
> 
> 
> See http://www.zope.org/Collectors/Zope3-dev/516

If you revisit this link, you will now see a follow-up by Jim Fulton.
This little unicode vs. 8 byte string has actually turned into a much
bigger problem revolving around many aspects of principal IDs. Let's
hope this can be properly fixed in Zope 3.3.

Zope 3.2 (which is going to be released at the end of this month or the
beginning of January) will have at least a temporary fix now: the
principal IDs will still be unicode, but will only contain ASCII which
means it'll always be str()able.

Therefore, if DirectoryStorage synced its behaviour with FileStorage
regarding the str()ing of principal IDs/user names, we would be safe
with Zope 3.2+ (and also with Zope 3.1 as long as principal IDs used
there are ASCII only).

Best regards

Philipp


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click