-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipenv run --help
thows excption
#2127
Comments
this is not a valid command, and calling |
|
Hey @halloleo, thanks for using pipenv! I can understand the frustration of what seems like inconsistencies in the api, however due to the way run works, we have to capture any flags and pass them down into the environment like @techalchemy said. If you have an idea of how to work around it let us know and submit a PR! |
The problem is that |
Thanks for the explanation. See whether I get to it. |
You are saying that pipenv forwards everything to the subprocess command line, that is not exactly true:
This command does not run As @uranusjr pointed out, there already exists a convention for distinguishing options and arguments for a given command in case of ambiguity: the
The only thing needed to enable |
I have created #3844 to fix this. |
In an empty directory (where isn't a
pipfile
in any of the searched parents) issue the commandand you get:
I use the follwoing PIPENV variables:
Once the virtual env is created and you issue again
pipenv run --help
you get still the same exception.The text was updated successfully, but these errors were encountered: