You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In VSCode notebooks, I have been able to keep functions in a process_data.py file placed in the same directory as a notebook I am working with. That way I can move functionality out of the notebook and into the .py module to keep the notebook clean.
As of the latest pre-release version, pylance does not resolve the import, and so does not know anything about the functions I am importing. It does work in a regular other.py file.
fails in notebook
works in regular .py files
I've awkwardly bypassed this using the following try-except. pylance recognises imports via the .process_data relative import, but this raises an importerror when called on its own in the notebook :(
Describe the bug
In VSCode notebooks, I have been able to keep functions in a
process_data.py
file placed in the same directory as a notebook I am working with. That way I can move functionality out of the notebook and into the .py module to keep the notebook clean.As of the latest pre-release version, pylance does not resolve the import, and so does not know anything about the functions I am importing. It does work in a regular
other.py
file.fails in notebook
works in regular .py files
I've awkwardly bypassed this using the following try-except. pylance recognises imports via the
.process_data
relative import, but this raises an importerror when called on its own in the notebook :(VS Code extension or command-line
Running Python extension pre-release version v2022.11.12021011
The text was updated successfully, but these errors were encountered: