[Zope-dev] getPhysicalPath differs for function vs. __getattr__

2001-12-06 Thread John Ziniti
Sorry the subject is not so discriptive, but here is the issue I am dealing with. I wonder whether this has to do with the way Zope deals with objects or has something to do with Python: I have an Python Product class Object. With the following bits of code, I get different results from a

Re: [Zope-dev] getPhysicalPath differs for function vs. __getattr__

2001-12-06 Thread Wolfram Kerber
] Sent: Thursday, December 06, 2001 5:06 PM Subject: [Zope-dev] getPhysicalPath differs for function vs. __getattr__ Sorry the subject is not so discriptive, but here is the issue I am dealing with. I wonder whether this has to do with the way Zope deals with objects or has something to do

Re: [Zope-dev] getPhysicalPath?

2001-03-18 Thread richard
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

Re: [Zope-dev] getPhysicalPath?

2001-03-16 Thread 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? -- Tom Jenkins

RE: [Zope-dev] getPhysicalPath?

2001-03-16 Thread Brian Lloyd
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

Re: [Zope-dev] getPhysicalPath?

2001-03-16 Thread Christian Scholz
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,

RE: [Zope-dev] getPhysicalPath?

2001-03-16 Thread Brian Lloyd
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

Re: [Zope-dev] getPhysicalPath?

2001-03-16 Thread Evan Simpson
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

RE: [Zope-dev] getPhysicalPath?

2001-03-16 Thread Michel Pelletier
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

[Zope-dev] getPhysicalPath?

2001-03-15 Thread Andy McKay
getPhysicalPath returns the physical path to an object ignoring how I got there through Acquistion. There are a bunch of variables in the REQUEST that tell me how I got to an object, but we have an object that is messing around with traversal, so the REQUEST variables arent ideal. Is there a

Re: [Zope-dev] getPhysicalPath?

2001-03-15 Thread Andy McKay
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 physic