-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attach to process takes a long time #1044
Comments
Closing (duplicate of #1003). Please see if #1003 (comment) fixes it for you (note: you need to set that environment variable in your system or in the shell that spawns VSCode). |
Reopening (I missed that it was in a different OS). |
I'm not sure how much this is something we can fix (6 seconds isn't that much time and unfortunately just importing libraries on Python is pretty slow). Historically we had to pre-load everything due to Python 2.7 deadlocking in lazy imports in the debugger due to its lock around imports... maybe we could revisit this now that Python 2 support is dropped to import less things at startup. |
It looks like we can't do much about this, unfortunately. |
Environment data
Actual behavior
Attaching the debugger to a python process running simple script takes a long time (around 6 seconds on my machine). This is reproducible on several other Windows machines.
Expected behavior
Attaching to a python process is faster (ideally less than 1 second).
Steps to reproduce:
script.py
:python script.py
python
process started in the previous step.The text was updated successfully, but these errors were encountered: