> On Sun, Feb 21, 2010 at 4:09 PM, Leo Soto M. <leo.s...@gmail.com> wrote: > [...] >> Under Jython it doesn't start a new process, but a new thread. The >> thread is started using thread.start_new_thread though, which makes it >> untraceable. > > For the sake of correctness I must say I shouldn't have used > "untraceable" here. There is nothing preventing the thread code to be > traced. It's just that the threading.settrace() hook only works for > threads started using the threading module, but not for the ones > started using the low-level thread module. >
An idea might be asking the Django guys to make it more friendly to debuggers so that this can be easier -- maybe even passing a patch to them -- this is one of the things I have in my checklist after the django integration is in place. Best Regards, Fabio ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pydev-code mailing list pydev-code@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-code
