Lucie Lejard wrote:
> Daniel Krech wrote:
>> On Dec 20, 2006, at 2:19 PM, Lucie Lejard wrote:
>>
>>> Hi,
>>>
>>> I am using the default profiler of zope (in zmi/Control_Panel/DebugInfo)
>>> to trace the calls when I go on a specific template.
>>> This template is using a Five view that has methods using the rdflib.
>>> You will see below the error i have when I try to access the template
>>> using the zope profiler:
>>>
...
>>> Module Products.RosettaArchive.tools.rdf, line 108, in getBrowser
>>> Module Products.RosettaArchive.tools.rdf, line 60, in getGraph
>>> Module rdflib.Graph, line 478, in __init__
>>> Module rdflib.Graph, line 101, in __init__
>>> Module rdflib.BNode, line 49, in __new__
>>> Module profile, line 231, in trace_dispatch_i
>>> Module profile, line 238, in trace_dispatch_i
>>> Module profile, line 291, in trace_dispatch_call
>>> AssertionError: ('Bad call',
>>> ('/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/rdflib/BNode.py',
>>>
>>> 42, '__new__'), <frame object at 0x4698e10>, <frame object at
>>> 0x1a06410>, <frame object at 0x44c5810>, <frame object at 0x18ab010>)
>>>
As a workaround, you might be able to patch getGraph with a version that
turns profiling off for that call only. hotshot has a stop() that I've
never tried, with regular profile you might have to unset the trace
yourself (sys.settrace).
_______________________________________________
Dev mailing list
[email protected]
http://rdflib.net/mailman/listinfo/dev
