Skip to content

Poor error message when pipenv couldn't be activated. #4866

@ericsnowcurrently

Description

@ericsnowcurrently

Screenshot from 2019-03-20 16-44-02

I have pipenv set up in my workspace folder. The extension picks it up. However, if it tries to activate the environment then I get an error pop-up. If I expand the pop-up, I see the following (formatted exactly) unhelpful message:

Workspace contains pipfile but attempt to run 'pipenv --
venv' failed with 'Traceback (most recent call last):  File 
"/home/esnow/.local/bin/pipenv", line 11, in <module> 
sys.exit(cli()) File "/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/core.py", line 764, in 
__call__ return self.main(*args, **kwargs) File 
"/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/core.py", line 717, in main
 rv = self.invoke(ctx) File 
"/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/core.py", line 1114, in 
invoke return Command.invoke(self, ctx) File 
"/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/core.py", line 956, in invoke 
return ctx.invoke(self.callback, **ctx.params) File 
"/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/core.py", line 555, in invoke 
return callback(*args, **kwargs) File 
"/home/esnow/.local/lib/python3.7/site-
packages/pipenv/vendor/click/decorators.py", lin...

The extension should fix up the error message (rather than dumping the full un-edited text).

Metadata

Metadata

Assignees

Labels

feature-requestRequest for new features or functionality

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions