Skip to content
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

using pip to resolve dependencies (but use Pipenv, and Pipenv.lock) #4777

Closed
franzhaas opened this issue Aug 28, 2021 · 2 comments · Fixed by #4759
Closed

using pip to resolve dependencies (but use Pipenv, and Pipenv.lock) #4777

franzhaas opened this issue Aug 28, 2021 · 2 comments · Fixed by #4759

Comments

@franzhaas
Copy link

franzhaas commented Aug 28, 2021

Dear all,

using jupyter-book and jupyterlab i ended up with an issue with dependency resolution.
(executablebooks/MyST-NB#355)

pip was able to resolve the dependencies. I personally would have prefered if my pipenv install would have resolved the dependencies, but this is propably down to a library that is used by pipenv...

What i realised at that point is that I may end up with different environments than my coleagues who dont use pipenv yet (Even if the pipenv install would have resolved the dependencies, the solution may not be the same that was found by a different tool.)

I hacked together this solution https://github.com/franzhaas/pipenv_by_pip which solves my problem at hand (so far).

Is this a recommendable workflow? Do you have better suggestions?

Thanks in advance,
Franz

@franzhaas
Copy link
Author

I just improved the script by checking for attempts to use a nested environment, and locking only once...

@florisla
Copy link

It looks like #4759 is trying to achieve the same thing -- use pip's resolver instead of the one of piptools.

@frostming frostming linked a pull request Nov 3, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants