|
|
|
|
|
by crabbone
1202 days ago
|
|
Python debugger is really sad for many more reasons: 1. Cannot interrupt a running program to get debugger prompt, you have to code that functionality in yourself. 2. Cannot deal with threads or multiple child processes because it gets confused by where its output should go, and so it appears to be stuck, prompt doesn't show up, or input isn't being accepted. 3. If someone writes an overly general except, debugger won't ever be called because in order to be called it relies on exceptions. 4. Debugger cannot evaluate comprehensions correctly due to scoping issues (not as much of a debugger fault as much of the language fault). 5. Debugger cannot consistently modify variables inside the function call. Depending on circumstances if you execute an assignment statement in debugger, the value may or may not be set to the variable in current stack frame. 6. Debugger doesn't step into iterator implementation (iirc, I might be confusing with tracing). |
|