unrestrictedTraverse fails if path contains //

[Jérôme Perrin]

If unrestrictedTraverse is called with a string path containing "//", it raise an IndexError. Currently, it splits the path using '/', iterates on the list of path elements, and checks if path[0] == '_' which raises a IndexError if the path element is an empty string.

One solution can be to skip the path element if it's an empty string at that point.

--- /usr/lib/zope/lib/python/OFS/Traversable.py 2003-12-10 18:53:31.000000000 +0100
+++ /home/jerome/Traversable.py 2006-04-05 15:54:47.931177500 +0200
@@ -143,6 +143,9 @@
                 name=pop()
                 __traceback_info__ = path, name

+ if name == '':
+ continue
+
                 if name[0] == '_':
                     # Never allowed in a URL.
                     raise NotFound, name

[Florent Guillaume (efge)]

Empty path elements have never been legal.

I'd rather raise a proper NotFound if one is found.

[ChrisW (chris-simplistix)]

Status: Pending => Rejected

I think an IndexError is just fine.

[Florent Guillaume (efge)]

Status: Rejected => Pending

IndexError is not fine. Nobody expects it to be returned from (un)restrictedTraverse so nobody will catch it.

[Jérôme Perrin (perrinjerome)]

// is valid in URLs and in ZPublisher.BaseRequest.traverse, so IMHO, it would be good to allow it in restrictedTraverse as well, for consistency.

[Colin Watson (cjwatson)]

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.