From: Roger B. <ro...@ro...> - 2003-09-15 22:47:05
|
> Yeah, I meant ot ask about this. Any pointers on python development? > How do you do it, Roger? Are you using something like IDLE, or > just prints, or what? I actually use xemacs to edit the code, and the occassional print statement for debugging. If things look really bad then I do fire up PythonWin and use the debugger in that. > others. Seemed to me it was an issue with the debugger and threads. Python isn't as wildly threaded as other languages. The interpretter itself has a single lock - GIL (aka Global Interpretter Lock). BitPim uses two threads. One does the gui, and one does the com port. > BTW, I tried bitpim on a different computer, and things were much > more stable, so I guess it was the computer. Maybe have something to > do with it being a dual CPU machine is my best guess. It could also be that the drivers for the cable were not SMP safe. It certainly isn't a fundamental issue with Python as it is used on all sorts of platforms with random numbers of CPUs, and the GIL makes it almost impossible to have the normal sort of race conditions and other wierdities you get with finely threaded code. Roger |