On Sat, 2009-06-20 at 13:04 -0600, Shane Hathaway wrote: > 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.
I think there's a valid goal around here. Publisher traversal and traversal as used in templates have two different implementations that partly overlap at some points and its hard to explain why there are two of them. I'm not sure whether we can get a single unified implementation, but for me that would be nice. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
