Jim Fulton wrote:
> Why? traverseName is part of zope.app.publication's implementation.
> Now it's oddly split off in a very separate package.
The publisher traversal code is very similar to the code in
zope.traversing, so I thought the best thing to do is put it in the same
package as zope.traversing, so that traversal would be maintained in one
> Or, better yet, traverseRelativeURL and traversePath should be moved
> to the browser module and should get traverseName from
> I'll go ahead and do this.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -