The VSCode extension djlint should not require people to install the Python package

[nbro]

Under the hood, the VSCode extension djlint should take care of installing djlint with pip or whatever in an isolated environment, which should be removed whenever we remove the extension. I shouldn't need to add this dependency to my pyproject.toml (with poetry) just to make the VSCode extension work.

[monosans]

You can use pipx

[nbro]

My point is that I shouldn't need to use any Python package manager (pip, pipx, pip-tools, poetry, whatever) to make the VSCode extension work. We should just need maybe Python and that's it. So, the Python package should be installed automatically, in some virtual environment, whenever we install the VSCode extension, and it should be removed automatically, along with the virtual environment, whenever we remove the extension

[isoboroff]

What if I have a global djlint installed (/opt/homebrew/bin/djlint, for example)?

The current behavior is to tell me to install djlint in the current venv.

[monosans]

What if I have a global djlint installed (/opt/homebrew/bin/djlint, for example)?

The current behavior is to tell me to install djlint in the current venv.

Please read the README