> > > > Then I don't know. > > (The application instance is none other than zope itself. ) > > I can honestly not think of a way to extract this information. I've > > even tried setting up a simple example method and I couldn't get hold > > of the zodb name of the external method that is called. > > You can go the low-level route: Using the inspect module, you can get to > the stack frames of your callers, and then inspect the local variables > there. There must be one that can get you the information you want. >
We tried that but no luck. > See the docstrings of the functions in the inspect module for details. > > Florent > > -- > Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D > +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] > -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
