-
Notifications
You must be signed in to change notification settings - Fork 131
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
debugpy 1.6.4 PermissionError
while debugging Jupyter Notebook in VS Code on MacOS
#1154
Comments
The change is that on I guess that the fix will be just ignoring the I'll provide a PR shortly... |
I am suspicious this bug was introduced by changes made for #1031
Environment data
Actual behavior
Debugging a Jupyter Notebook in VS Code with debugpy 1.6.4 fails with a
PermissionError
on MacOS when the debugger tries to debug into a Python source file. This seems to be particularly an issue when trying working with a file on a Google Drive Volume.Debugging works as intended if I install debugpy 1.6.3 by
pip install debugpy==1.6.3
This has been tested on Python 3.8/3.10/3.11 with the same results.
Error Message:
(Personal identifiers removed)
The error occurs specifically when trying to debug code that should trigger opening another window to display code in a Python file.
It seems the use of Google Drive is relevant here because trying to list the contents of the directory does cause a
PermissionError
:Expected behavior
I would expect debugpy to not be listing the contents of all directories above the Jupyter notebook being worked on,
or at list be able to recover from a PermissionError, as previous versions of debugpy have done.
Steps to reproduce:
test.py
in the Google Drive Volume. (The file can be blank)test.py
test_notebook.ipynb
and save it to the same folder.import test
(Brownie points for finding a bug that intersects with software from Microsoft, Apple, and Google?)
The text was updated successfully, but these errors were encountered: