Feb 16, 2020 · Environment data VS Code version: 1.42.1 Extension version (available under the Extensions sidebar): Not sure OS and version: Windows 10. Version 10.0.18362 Build 18362 Python version (& distribution if applicable, e.g. Anaconda): 3.6.0 ...
16.06.2021 · If i run the same on IDLE (python3.9) the code works, which leads me to believe that this is a VScode issue, but i cannot tell what this is or how to fix it. In fact, if i recreate new folders in VS code, the imports work too.
Mar 11, 2019 · Environment data VS Code version: 1.28.0 Extension version (available under the Extensions sidebar): 2018.8.0 OS and version: Windows 10 Professional 64bit 10.0.17134 Build 17134 Python version (& distribution if applicable, e.g. Anacond...
05.11.2019 · Unfortunately I'm not exactly able to repro it right now. Which is to say, my environment is set up correctly and working in VSCode now and I'd rather not spend the time breaking down my environment to try and getting this cacheing issue to repro. But, I think the old issue has a good amount of information and ends aptly: It's a bug in VSCode.
Jun 17, 2021 · If i run the same on IDLE (python3.9) the code works, which leads me to believe that this is a VScode issue, but i cannot tell what this is or how to fix it. In fact, if i recreate new folders in VS code, the imports work too.
24.04.2020 · This is often because the Python interpreter that VS Code uses for inspect your project (to provide auto-complete) and the interpreter used for running your code in Terminal is different (hence, in different environment and having their own list of installed packages).
Apr 24, 2020 · This is often because the Python interpreter that VS Code uses for inspect your project (to provide auto-complete) and the interpreter used for running your code in Terminal is different (hence, in different environment and having their own list of installed packages).
02.05.2020 · This is microsoft/debugpy#281. The bug is that the exception is reported incorrectly when it shouldn't be, but it doesn't actually break your app - if you press F5, it should continue running. To prevent it from being reported, uncheck "User-Unhandled Exceptions" in the Breakpoints pane in bottom left.
I'm installing Python and VSCode on a new computer, and I remember the process being a ... running python from the command prompt, I don't get an error.
That's absolutely fine. No rush on my end - this isn't for a production environment but more of a side-project. There is absolutely a possibility it is a configuration problem, but I think I've exhausted enough paths to ensure it's at least not an obvious configuration issue (though maybe it is!) - but I've done enough to convince myself there is a decent possibility it is a valid bug so …
Apr 16, 2019 · In order to import the NotaParcial class in our run.py we simple do: The someclass after the from keyword represents the folder which you are importing from. the NotaParcial class is the class which is available in the __init__.py. The __init__.py initialized the folder its in as a module.
11.03.2019 · Yup, it was VSCode's fault. Reinstalling it fixed the issue, because I removed the "pythonPath": "${config:python.pythonPath}" from the launch.json and it still works. Also renamed my module's folder name and renamed it in the code and it works.
May 02, 2020 · This is microsoft/debugpy#281. The bug is that the exception is reported incorrectly when it shouldn't be, but it doesn't actually break your app - if you press F5, it should continue running. To prevent it from being reported, uncheck "User-Unhandled Exceptions" in the Breakpoints pane in bottom left.