A look into workflow tools - package management in the Python extension for VS Code

[brettcannon]

@groodt

his looks like a great quality of life improvement for new and experienced python developers. It’s also not locking anyone into VS Code and seems to play well with the built-in and standards-centric tooling.

Thanks! We never want to lock anyone into VS Code, hence why we are limiting ourselves to things people could do on their own in a shell or via some other manual step(s).

@pf_moore

If you start with pyproject.toml, you will definitely need to change later, because pyproject.toml can’t support all the use cases for requirements.txt

It honestly doesn’t need to. We only care about beginners and providing an opinionated flow for the common case. We are going into this knowing full well we won’t be able to come up with something for everyone or something that even intermediate/advanced users will necessarily want.

@pf_moore

What would definitely be a step backwards is to create a new generation of programmers who expect to have a tool to manage pyproject.toml

Are you saying that’s okay for requirements.txt? Or are you suggesting we don’t write down what a user wants to install or has installed (if PEP 710 - Recording the provenance of installed packages is accepted)?

@pf_moore

doesn’t make the effort to preserve formatting

I wouldn’t let that ship/happen.