locals behaviour different between debug and start without debugging
See original GitHub issueEnvironment data
VS Code version: 1.19.2 Python Extension version: 0.9.1 Python Version: 3.6.3 OS and version: Mac OS X 10.13.2
Actual behavior
VS Code debug behaviour different than “start without debugging”
Expected behavior
VS Code should respect development locals configuration when debugging but seems to be operating in different environment.
Steps to reproduce:
Run code with debugging and without debugging and different locals will be used.
Logs
Output from Python
output panel
Output from Console window
(Help->Developer Tools menu)
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
The difference between “Start with debugging ... - Dynamsoft
In the “Start with debugging” mode, iHowMany is initialized to 0. But in the “Start without debugging” mode, the value of iHowMany is...
Read more >Back to Basic : Difference between Start Debugging & Start ...
In this post we are going to talk about yet another very basic, simple topic but seems confusing among many beginners – 'Start...
Read more >c++ - Different behaviour running from command line to "Run ...
Command-line and startup folder are exactly the same. Any other differences between "start without debugging" and real release mode? – Anteru.
Read more >Program Runs Slower When Using "Start Without Debuggin"
When I execute the program by "Start without Debugging" the code takes between 2 and 3 times longer. Same dataset. No recompiles.
Read more >Debugging configurations for Python apps in Visual Studio Code
Details on configuring the Visual Studio Code debugger for different ... the Debug Panel, F5 or Run > Start Debugging when no configuration...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi yes, I have just updated my visual studio and run it in the new debugger and it has resolved the issue.
I believe the issue has been resolve with the new debugger. Please install the latest development version of the extension from here to validate it (https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build). Please feel free to re-open the issue or comment on it and I’ll open it.