'Bad return' profiler assertion error in python 2.2, worked in <=2.1
Matthew Mueller
donut at SaPzAsMtarnet.com
Tue Jan 22 21:28:22 EST 2002
In article <3C3E2308.1060606 at skippinet.com.au>, Mark Hammond wrote:
> Matthew Mueller wrote:
>
> [snip tale of woe regarding assertions in the profiler]
>
> I had the exact same problem - so I commented out the assertions, and it
> worked fine. I then promptly forgot about it :)
Unfortunatly, commenting the assertions out doesn't seem to be enough
for my problem.
Then I just get:
Traceback (most recent call last):
File "/x/donut/usr/python-cvs/lib/python2.2/site.py", line 310, in ?
import sitecustomize
File "/x/donut/usr/python-cvs/lib/python2.2/site-packages/sitecustomize.py", line 1, in ?
import pyprof_auto #if PYPROF is set, profile automatically.
File "/x/donut/usr/python-cvs/lib/python2.2/profile.py", line 214, in trace_dispatch_i
if self.dispatch[event](self, frame,t):
File "/x/donut/usr/python-cvs/lib/python2.2/profile.py", line 281, in trace_dispatch_return
self.trace_dispatch_return(self.cur[-2], 0)
File "/x/donut/usr/python-cvs/lib/python2.2/profile.py", line 290, in trace_dispatch_return
ppt, pit, pet, pfn, pframe, pcur = rcur
TypeError: unpack non-sequence
--
Matthew Mueller
Noone likes spam in their email.
More information about the Python-list
mailing list