It must be generating an error message like "unexpected semicolon on line 31", but I don't know where to look. Visual Studio also provides tight integration between the Python code editor and the Interactive window. As my code size grows this is becoming unworkable staring works better on a short test program than on a longer more product oriented program. Then I stare at the code until I see the syntax error, fix it, repeat the same process and the debugger starts and steps to "main". It doesn't report an error message (or any problems). VS "thinks" for anywhere from a few milliseconds to several seconds.Īnd then nothing.To dismiss whole line completions, the Esc or Delete keys can be used. This will change the accept key from Tab to the right arrow ->. Solution: Launch VS Code from a Terminal/Command window with the correct virtual environment activated. The path to the custom modules is set when a virtual environment is activated. Cause: VS Code was not launched from the active virtual environment. Enable the setting named Apply completions for whole lines on right arrow. Remember to re-start VS Code once done (this won’t be necessary in a future release). VS Code launches and opens the correct file. To change the default accept key, go to Tools -> Options -> IntelliCode -> Completions for whole lines of code.I click the DEBUG button in the scrip window.Every time I make such an error the following happens: I'm more of a C++ guy and make a lot of little syntax errors when writing Python code. In the new VS Code debugger (which is mostly working well for me (and which I like much better than the old IDE)), I can't figure out where syntax errors are reported.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |