__getattr__ gets the 'true self' as argument while other methods always get
an acquisition wrapped self, this is by design. Usually it's not a good idea
to override __getattr__ of acquisition aware objects.
- Original Message -
From: John Ziniti [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Brian Lloyd wrote:
Is there a simple method like getAcquistionPath() that tells
me how I was
required without having to do some sub optimal REQUEST
variable hacking /
string matching?
I don't know of any (but that doesn't mean there isn't one). But
couldn't you walk up the
Is there a simple method like getAcquistionPath() that tells me how I was
required without having to do some sub optimal REQUEST variable hacking /
string matching?
I don't know of any (but that doesn't mean there isn't one). But
couldn't you walk up the aq_parent?
--
Tom Jenkins
Is there a simple method like getAcquistionPath() that tells
me how I was
required without having to do some sub optimal REQUEST
variable hacking /
string matching?
I don't know of any (but that doesn't mean there isn't one). But
couldn't you walk up the aq_parent?
Acquisition
Hi!
Ahh... thanks Brian. Thats a new one to me :)
To me, aswell. Is this documented somewhere? ;-)
And can someone explain to us where the differences between
aq_chain and getPhysicalPath() are? Actually getPhysicalPath()
seems also to walk up aq_parent. Or am I missing something?
regards,
To me, aswell. Is this documented somewhere? ;-)
It's not in the Acquisition.stx in the ExtensionClass docs -
probably they were never updated when it was added. I think
that aq_chain is most useful as a debugging aid rather than
something one would use in an application (which is not to
From: "Christian Scholz" [EMAIL PROTECTED]
And can someone explain to us where the differences between
aq_chain and getPhysicalPath() are? Actually getPhysicalPath()
seems also to walk up aq_parent. Or am I missing something?
"aq_chain" gives you a list of the objects traversed to get to your
On Fri, 16 Mar 2001, Brian Lloyd wrote:
To me, aswell. Is this documented somewhere? ;-)
It's not in the Acquisition.stx in the ExtensionClass docs -
probably they were never updated when it was added. I think
that aq_chain is most useful as a debugging aid rather than
something one
Should be "how I was acquired" not required. Duh.
--
Andy McKay.
- Original Message -
From: "Andy McKay" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 15, 2001 6:26 PM
Subject: [Zope-dev] getPhysicalPath?
getPhysicalPath returns the physical path to an object
