20 Jun
2009
20 Jun
'09
7:04 p.m.
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 place.
Or, better yet, traverseRelativeURL and traversePath should be moved to the browser module and should get traverseName from request.publication.
I'll go ahead and do this.
That's fine. Shane