[Zope3-dev] Notations for paths

[Jim Fulton]

Steve Alexander wrote:
> Jim Fulton wrote:
> 
>> Phillip,
>>
>> I agree with your arguments about using objects for paths. I think that,
>> as usual, they are well reasoned and persuasive.
>>
>> But :)
>>
>> In the case of paths, I'd like to stick with unicode strings for the
>> simple reasons that:
>>
>> - People are very accustomed to using strings to express paths,
>>
>> - Paths are used all over the place, so it should be really easy
>>   to express them,
>>
>> - Paths will often be used in places where it's inconventient to
>>   call constructors to create objects.
>>
>> I would like to stop using sequences as an alternate canonical
>> representation. I think that this was a mistake on my part in the
>> first place.
>>
>> Does anybody want to try to take this refactoring job on before
>> the alpha?
> 
> 
> I can take it on for the ObjectHub package.

I was thinking more in terms of Zope.App.Traversing.

Jim


-- 
Jim Fulton           mailto:jim@zope.com       Python Powered!
CTO                  (888) 344-4332            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org