El 17 Oct 2008, a las 10:37 , Christian Theune escribió:
There is a process that actually needs the request and this process
is
what I call traversal: breaking down a URL and finding a publishable
object. zope.traversing has (almost) nothing to do with it, the real
kind of traversal happens
On Oct 15, 2008, at 12:02 PM, Philipp von Weitershausen wrote:
Christian Theune wrote:
we stumbled over an annoyance that took a while to debug:
Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
(non-multi)
El 17 Oct 2008, a las 15:02 , Jim Fulton escribió:
First of all, its name is quite misleading. It should really be
called
'zope.resolvepath' because it resolves TALES-like object paths. In
fact,
it's pretty much only used by the PageTemplate machinery to hook it
up
to the TALES
On Friday 17 October 2008, Jim Fulton wrote:
It would be nice to deprecate zope.traversing and fold it into
zope.app.pagetemplate.
Just skimming the thread, wouldn't this make it harder for us to integrate
z3c.pt, which also needs those traversal APIs?
Regards,
Stephan
--
Stephan Richter
On Oct 17, 2008, at 1:13 PM, Stephan Richter wrote:
On Friday 17 October 2008, Jim Fulton wrote:
It would be nice to deprecate zope.traversing and fold it into
zope.app.pagetemplate.
Just skimming the thread, wouldn't this make it harder for us to
integrate
z3c.pt, which also needs
Previously Jim Fulton wrote:
On Oct 17, 2008, at 1:13 PM, Stephan Richter wrote:
On Friday 17 October 2008, Jim Fulton wrote:
It would be nice to deprecate zope.traversing and fold it into
zope.app.pagetemplate.
Just skimming the thread, wouldn't this make it harder for us to
Hi,
we stumbled over an annoyance that took a while to debug:
Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
(non-multi) adapter and ended up with a working test.
In the actual system, we found that the
Christian Theune wrote:
we stumbled over an annoyance that took a while to debug:
Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
(non-multi) adapter and ended up with a working test.
In the actual system,
On Wed, Oct 15, 2008 at 06:02:55PM +0200, Philipp von Weitershausen wrote:
Christian Theune wrote:
we stumbled over an annoyance that took a while to debug:
Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
Philipp von Weitershausen wrote:
First of all, its name is quite misleading. It should really be called
'zope.resolvepath' because it resolves TALES-like object paths. In fact,
it's pretty much only used by the PageTemplate machinery to hook it up
to the TALES engine (with one exception,
El 15 Oct 2008, a las 19:24 , Shane Hathaway escribió:
Philipp von Weitershausen wrote:
First of all, its name is quite misleading. It should really be
called
'zope.resolvepath' because it resolves TALES-like object paths. In
fact,
it's pretty much only used by the PageTemplate machinery
11 matches
Mail list logo
