Transitioning `launch.json` from no live re-loading to live re-loading of flask and django

[DonJayamanne]

Currently live reloading of Flask and Django is disabled in the launch.json.
With multi-process debugging support, this will no longer be necessary.

We'll also need to provide a mechanism to upgrade the existing launch.json values

Options:

1. When user starts debugging flask/django, we check these values and display a prompt:
   • Ask if they want live reloading [yes], [no], [ignore always]
   • Optionally update the launch.json accordingly (or provide instructions to user)
2. When user opens a workspace with launch.json that has flask and django debug configurations (almost everyone who has debugged Python will have it), we display a prompt and make the changes in launch.json
   • Problem: Almost all users will have Flask and Django configs in launch.json, hence this prompt will be displayed to all users.
   • Problem: This will be a challenging task as launch.json is technically not a valid json document, hence I'd prefer to avoid this.

[1st]

Question: can I run debug without --noreload flag for Django project? I have used it all the time, but it will be good to have code re-loaded automatically when my Django project is running in debug mode via VS Code.

[1st]

OK, I see that when I remove the --noreload from args the process can't be stopped automatically by VS Code for some reason and I need to do ps ax | grep manage.py and kill the process.

Any updates about this ticket yet?

[luabud]

This is now done (dupe of #3097)