You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.
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)?
The text was updated successfully, but these errors were encountered:
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
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).
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)?The text was updated successfully, but these errors were encountered: