I've been experimenting with using pip-compile for Jinja, and have run into an interesting circular dependency between Jinja and Sphinx. Jinja uses an editable install (-e .) for development. Jinja lists Sphinx in requirements.in for bui...
{"name":"Python: Flask","type":"python","request":"launch","module":"flask","env": {"FLASK_APP":"app.py"},"args": ["run","--no-debugger","--no-reload"],"jinja":true}, {"name":"Python: Current File (External Terminal)","type":"python","request":"launch","program":"...
"name": "Flask", "type": "python", "request": "launch", "module": "flask", "env": { "FLASK_APP": "flasker.py", "FLASK_ENV": "development", "FLASK_DEBUG": "0" }, "args": [ "run", "--no-debugger", "--no-reload" ], "jinja": true }, where flasker.py. is the...
Preferring the blueprint template folder over the application's template folder would break the existing contract between app's and blueprints. This contract is used to much success across the extension ecosystem. For example, the Flask-Security extension mounts a blueprint to an application and co...
{ "name": "Python: Flask", "type": "python", "request": "launch", "module": "flask", "env": { "FLASK_APP": "app.py" }, "args": [ "run", "--no-debugger", "--no-reload" ], "jinja": true }, { "name": "Python: Current File (External Terminal)", "type": "...