-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Debugger crashes when using Django's Development Server with a Proper Launch Profile #4988
Comments
I can confirm this bug:
As quick fix use the following launch.json
|
This works on my setup as well, with "--nothreading" commented out (I have always been commenting out "--nothreading" as suggested by VSCode docs, considering that I normally develop on Chromium).
|
Yup, Confirmed. It happens with the new update. |
This has been resolved upstream and we'll be shipping a fix for this. |
Environment data
Expected behaviour
Using the Python Extension on Visual Studio Code to run Django's development server as explained in the docs, https://code.visualstudio.com/docs/python/tutorial-django#_create-a-debugger-launch-profile, without any problems.
Actual behaviour
Can't use the debugger to launch Django's development server; As soon as you try to use the site, the debugger pauses on the exception VariableDoesNotExist, even on a fresh Django Project.
The problem does not manifest itself when using a previous version of the Python Extension (such as 2019.2.5558), nor it manifests itself when running Django's development server from a shell, or even from VS Code's Terminal.
Steps to reproduce:
Logs
Impossible to get the output as explained from the Output panel in Python: it is empty and the development server doesn't show any problem. Everything works fine if running Django's development server from a shell or from the terminal. The log below is the message shown in red (as shown in the screenshot) with the VariableDoesNotExist exception.
Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The following is a screenshot of everything explained above. Chrome just hangs. No page or error is shown. Thanks for your precious work.
The text was updated successfully, but these errors were encountered: