Thread: [Pydev-users] [pydev - Users] cannot see variables after psyco import
Brought to you by:
fabioz
From: SourceForge.net <no...@so...> - 2006-10-20 20:15:25
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3973404 By: knovak The variables all say "cannot resolve variable" after I import psyco. This is before I actually tell psyco to compile anything. I execute this in the debugger: b=100 import psyco print b with breakpoints before & after the import. Any ideas how to get around this? I want psyco in my released code but am tired of commenting out each psyco import to debug. Thanks Kim ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 |
From: SourceForge.net <no...@so...> - 2006-10-20 22:49:01
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3973553 By: fabioz Well, I've taken a look at that, and the problem seems to be that psyco 'drops' the frames from a thread and creates a new set of frames -- just by importing it (and the debugger is still attached to the old set of frames). Please report that as a bug. Now, you can have a little better structure instead of commenting out your code -- something like having a module that imports psyco: file: mypsyco.py if RELEASE: from psyco import * else: ... do your own wrappers for the functions that you use from psyco an no-ops. This way you could just pass a parameter to set that RELEASE flag... Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 |