search

tox-dev / tox-pipenv

A pipenv plugin for Tox
MIT License
124 stars 30 forks source link

Support `-p` / `--pipfile` for deps section #58

Open bittner opened 5 years ago

bittner commented 5 years ago

If I'm not totally mistaken a -p / --pipfile option is not yet supported by this tox plugin. (This feature has been discussed in https://github.com/tox-dev/tox-pipenv/issues/37#issuecomment-397909182 and https://github.com/tox-dev/tox/issues/417#issuecomment-397910245, for example.)

I'm having a hard time accepting the fact that I need to continue using requirements.txt when I have a Pipfile. Can we add this feature here to make it easier to use Tox and Pipfile together (obsoleting the need for requirements.txt, obviously)?

bittner commented 5 years ago

Interesting! There is a tox-pipenv-install package on PyPI, which is mentioned in the Tox docs. The implementation is almost just a code snippet. Can we re-use this? (Sorry, if that is rude!)

tonybaloney commented 5 years ago

hi @bittner

please could you explain what you're wanting to do, this plugin is a bit confusing between pip, pipfile, tox and virtualenv's as to who is calling whom?

If there is a Pipfile in the project, it will copy that to each venv that tox creates and use it to install/setup the virtual environment

bittner commented 5 years ago

I was trying to transition from the -rrequirements.txt to a -p Pipfile syntax in deps sections, e.g. when I need the production dependencies installed plus some testing tools (in the same list).