-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Pip dependency resolution conflict with requirements.txt #63
Comments
I think this is a pretty big challenge. It seems to me that sphinx 4.0 has been quite controversial.
|
I'm trying to run things with:
but i get an error called:
|
I presume that this is the focus of |
To some degree - splitting up the "build" dependencies (e.g. the executablebook project deps) and the dependencies needed to actually run the notebooks can help IME, but it still might require some tweaking to get everything installed. |
My guess is that something happened in pip to update their "solver" which is causing these headaches. |
Yeah there are multiple potential failure modes. Changes to the pip resolver have caused problems recently, see e.g. pypa/pip#10201, but there have also been dependency conflicts between e.g. jupytext and myst-nb (e.g. executablebooks/MyST-NB#333) |
is there a solution that includes downgrading pip? |
Sorry for the off-topic post, but this is such an ironically relevant story for the scikit-image 1.0 transition! 😂 I'm very glad the discussion settled on skimage2. |
issue to follow |
FYI I tested the requirements.txt with the changes I am proposing here: pypa/pip#10479 And it didn't get stuck backtracking but very quickly gives the error:
|
The first step of
make html
ispip install -q -r requirements.txt
, but unfortunately it is not currently possible to install the dependencies with pip due to conflicts in pip's dependency resolver. The failure mode is particularly frustrating because it sendspip
down a path where it tries to download very old versions of e.g.pytest
and will only fail after these fail to build.I've encountered this problem before with the executablebooks project (executablebooks/MyST-NB#333, executablebooks/MyST-NB#289) so I suspected jupyter-book/jupytext as the culprit. Indeed, if jupyterbook and jupytext are removed from the requirements file and installed separately, the failure is resolved.
The text was updated successfully, but these errors were encountered: