Repository navigation
Allow Disabling Pipenv Check #1612
Description
When I start VSCode with the vscode-python extension I get the warning:
Workspace contains pipfile but attempt to run 'pipenv --venv' failed
I don't need pipenv support and my venv is inaccessible within a virtual machine anyway. It would be nice if there were a setting to prevent vscode-python from trying to run pipenv even if there is a Pipfile in the workspace.
Activity
brettcannon commentedon May 4, 2018
Do you want to take this on, Eric Snow (@ericsnowcurrently) , since I know you have talked about this?
DonJayamanne commentedon May 4, 2018
Shouldn't we removing the
needs decisionlabel? Or do we need to decide on the UX?sliedig commentedon Jun 16, 2018
brettcannon commentedon Jun 18, 2018
Stephen Liedig (@sliedig) please open a separate issue as what you're reporting is different than what this issue is about.
ncoghlan commentedon Jul 1, 2019
Not sure if this should be a separate issue, but this check failing seems to result in the extension giving up on running pylint over my code, even though I have
python.pythonPathset to a suitably configured environment.The reason I'm not sure if it should be a separate issue is because I think "Disable pipenv for the affected workspace" would be a perfectly acceptable answer (it's only broken because I haven't migrated the working directory into WSL yet, so editing the code from the Windows side works, and pylint mostly works, but the full environment won't come up as it includes Linux-specific bits)
brettcannon commentedon Jul 3, 2019
Alyssa Coghlan (@ncoghlan) yep, it's a separate issue. 😄 Please file one so we can flag it as a bug and look into it.
kimadeline commentedon Oct 21, 2021
We changed the way we perform environment discovery, and do not display this warning anymore.