Fred Drake wrote:
On 11/5/06, Stephan Richter <[EMAIL PROTECTED]> wrote:
This is officially an implementation detail;
zope.traversing.api.getName() is
the API call.
Interesting; I'd never known it was anything other than __name__.
These APIs just keep changing...
No, the APIs haven't change
On 11/5/06, Stephan Richter <[EMAIL PROTECTED]> wrote:
This is officially an implementation detail; zope.traversing.api.getName() is
the API call.
Interesting; I'd never known it was anything other than __name__.
These APIs just keep changing...
(Er, this indicates a serious documentation prob
On Sunday 05 November 2006 13:58, Gary Poster wrote:
> On Nov 5, 2006, at 1:12 PM, Peter Bengtsson wrote:
> > In Zope2 every object has an 'id' which meant that you can use
> > someobject.getId() to find out what name the object is stored under
> > in its container.
> > Is there an equivalent i
On Nov 5, 2006, at 1:12 PM, Peter Bengtsson wrote:
In Zope2 every object has an 'id' which meant that you can use
someobject.getId() to find out what name the object is stored under
in its container.
Is there an equivalent in zope3?
__name__
___
Peter Bengtsson wrote:
> In Zope2 every object has an 'id' which meant that you can use
> someobject.getId() to find out what name the object is stored under in
> its container.
> Is there an equivalent in zope3?
> ...or am I looking for a solution to a problem that doesn't exist?
Hi, Peter
Have a
In Zope2 every object has an 'id' which meant that you can use
someobject.getId() to find out what name the object is stored under in
its container.
Is there an equivalent in zope3?
...or am I looking for a solution to a problem that doesn't exist?
--
Peter Bengtsson,
work www.fry-it.com
home ww
