Skip to content
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.

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

Open
bittner opened this issue Dec 7, 2018 · 3 comments
Open

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

bittner opened this issue Dec 7, 2018 · 3 comments

Comments

@bittner
Copy link

bittner commented Dec 7, 2018

If I'm not totally mistaken a -p / --pipfile option is not yet supported by this tox plugin. (This feature has been discussed in #37 (comment) and tox-dev/tox#417 (comment), 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
Copy link
Author

bittner commented Dec 7, 2018

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
Copy link
Collaborator

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
Copy link
Author

bittner commented Feb 7, 2019

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).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants