Closed JHowell45 closed 5 years ago
This plugin should be used outside of pipenv. Don’t use pipenv run tox
because it’ll cause the loop you saw. Just call tox within the venv
So should I run something pipenv shell
--> tox
or just run tox
from the application directory?
nm I found out haha, I need to run pipenv shell
and then tox
. Why is that by the way if you don't mind me asking?
Pipenv doesn’t have a Python API (by design) so this plugin has to call it on the command line and also set a collection of environment variables to make it behave in a specific way.
Ahh ok thank you. For some reason now when running pipenv run tox
it works, i think it was due to when I ran pipenv shell
, tox
it may have fixed something which is weird, from now on I'll switch to using pipenv shell
, tox
Whenever I try to run
pipenv run tox
it tries to run/venv/bin/python -m pipenv graph
. Basically the same as runningpipenv
insidepipenv
failing becausepipenv
isn't a dependency. I have a temporary work around by installingpipenv
as a--dev
dependency, but was wondering if this was an issue with how tox gets executed from withinpipenv
due to howtox-pipenv
works?