-
-
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
Support --system
to pipenv sync
#2227
Comments
+1 |
I just tried aca8e12 from @frostming's branch, and it works as expected in my usecase (see https://travis-ci.org/evolution-events/Artaxerxes/jobs/382857314). Thanks! |
Hey, just in case pipenv uses Tox's virtualenv directly, with no intervention needed. ( for example https://circleci.com/gh/txomon/mosbot/17) |
I really would appreciate having It seems that this issue has stalled. Would it make sense to take |
Is there any difference between I'm currently using Update: Found an explanation in #3150, it seems that using the |
I've managed to get |
+1 |
there is a workaround which I'm using in my deployments. in CI, I will check if pipenv install --deploy then, during creation of Docker images, I don't include rm Pipefile
touch Pipefile
pipenv install --ignore-pipfile --deploy --system It is the fastest method I found. |
I'm trying to install dependencies inside of tox, which I believe needs
--system
(to install into tox's virtualenv instead of into pipenvs own virtualenv). See also #154.However,
pipenv sync
, which is the new way to install dependencies fromPipfile.lock
does not support--system
(it seems it was intentionally left out initially in #1463), so I have to resort topipenv install
.It seems it would be useful to support
--system
for sync as well.The text was updated successfully, but these errors were encountered: