|
-------- Original Message --------
John Anderson wrote: > There has be a flurry of questions about debugging threads. Have you > made any improvements in how threads are debugged in wing, or can you > explain why it's hard to implement a python debugger that handles threads? If you only want to debug a single thread, such as the a background thread, you can use a similar trick with Wing and import wingdbstub in the thread to be debugged. Using wingdbstub is the mechanism of having Chandler connect back to Wing. This is essentially how our Zope 2 support works so I'm confident that it will work, but debugging will be limited to the single thread. As far as why general threading hasn't been implemented, it's mainly a question of finding time to do it. Some of Wing's internal code needs to be changed and there might be a few things that need to be worked around in the interpreter. More and more people are asking for this, but it won't be in 2.1 which is very close to going out the door as a beta release. Possibly, we can add some basic support after 2.1 is out. John |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
