Offer a "add to requirements.txt" code action when package is installed

[luabud]

This is another idea which would be a precursor to #21555 is to offer a code action to add a missing dependency (probably matching an allow list) to requirements.txt.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[luabud]

cc @karthiknadig @cwebster-99

[karthiknadig]

What do you mean by Code Action in this context? It will depend on where they initiate the install, from a terminal or from python code in the editor.

In the terminal: I think we will need problem matcher for this that detects missing module first, then we could provide an action on that problem.

In code: if pylance is already initiating the install, then this could be something pylance can already handle?

[jongio]

This is the context of where I'd like to add a missing dependency to requirements.txt

[karthiknadig]

Adding an item to requirement.txt has some limitations. If the requirement.txt was built using some tool like pip-tools or has hashes then we can't add it to requirements. If it is plain requirements.txt then we could add it.

Another thing is what happens when there are dev-requirement.txt or test-requirement.txt or if there is a requirements directory with *.txt under it. There is probably some UI flow that is needed to handle these.

[brettcannon]

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.