-
Notifications
You must be signed in to change notification settings - Fork 68
pydevd errors (NoneType not attribute add_command; PyDB no attribute _py_db_command_thread_event) #1688
Comments
Can you give the full tracebacks? All errors seem to imply that The first error appears to be because a new process is created (but without the full traceback I can't say whether this is new process from a fork or a new process through subprocess or exec). |
(edited first post.) Further details: doesn't occur with Python 3.7.3 |
I see the error... ouch, it seems that during the initialization of the debugger a process is spawned (for I think you can work around it locally by editing:
then, in the first line in
Please let me know if that works... (it seems this is something that changed on Python itself). |
Thanks a lot. I reverted to Python 3.7.3 and solves the problem, which supports your theory. Tried your fix and solved the problem. What can we do to solve this issue? |
I'll create a patch for this shortly... |
Same error for me in eclipse 4.13 and 4.16 on Windows 10 with pydev 7.6.0 (was not experiencing on prior pydev. Python 3.7. The error happened for me around this code in pydevd: I tried fix above and turned into an endless busy cursor. My context was calling pdev breakpoint(). I can live with the error for now as it just spews junk that I can fix the bug that cause the breakpoint. But would be nice to have fixed! Not much fun. |
@lhughes41 if it's an issue in plain Also, please make sure you include your full stack trace and details on how you're reproducing your issue (since the original error should be fixed you probably have a different problem). |
Hi @fabioz |
Environment data
Actual behavior
Expected behavior
no errors.
Steps to reproduce:
(bash)
(python)
The text was updated successfully, but these errors were encountered: