On Thu, Sep 23, 2010 at 10:20 AM, Stephan Richter
<email address hidden> wrote:
> On Thursday, September 23, 2010, Jim Fulton wrote:
>> Perhaps it would be nice if the user field was unicode. <shrug> The
>> definition of this interface predates unicode in Python. This is
>> unlikely to change.
>>
>> A more likely change is to drop these fields altogether and keep just
>> the extension data, which allows any picklable data.
>
> What about simply using UTF-8 in zope.app.publication to encode and decode the
> principal id. This would require the smallest code change.
I doubt it would be much smaller than:
t.setUser(u) -> t.setExtendedInfo('user', u)
IIRC the publisher already uses extended info for the description/url.
On Thu, Sep 23, 2010 at 10:20 AM, Stephan Richter publication to encode and decode the
<email address hidden> wrote:
> On Thursday, September 23, 2010, Jim Fulton wrote:
>> Perhaps it would be nice if the user field was unicode. <shrug> The
>> definition of this interface predates unicode in Python. This is
>> unlikely to change.
>>
>> A more likely change is to drop these fields altogether and keep just
>> the extension data, which allows any picklable data.
>
> What about simply using UTF-8 in zope.app.
> principal id. This would require the smallest code change.
I doubt it would be much smaller than:
t.setUser(u) -> t.setExtendedIn fo('user' , u)
IIRC the publisher already uses extended info for the description/url.
Jim
--
Jim Fulton