Issue with jupyter-book 0.11 and pip-compile
See original GitHub issuemaintainer summary: jazzband/pip-tools#1372, is causing pip-compile to currently fail with jupyter-book v0.11, this should be fixed with jupyter-book v0.12
Describe the bug
The pinning of markdown-it-py
is inconsistent.
To Reproduce
molpopgen@pop-os:/venvs$ python3 -m venv test
molpopgen@pop-os:/venvs$ source test/bin/activate
(test) molpopgen@pop-os:/venvs$ echo "jupyter-book" > requirements.txt
(test) molpopgen@pop-os:/venvs$ pip install pip-tools
Collecting pip-tools
Using cached pip_tools-6.1.0-py3-none-any.whl (44 kB)
Collecting click>=7
Using cached click-8.0.1-py3-none-any.whl (97 kB)
Collecting pip>=20.3
Using cached pip-21.1.2-py3-none-any.whl (1.5 MB)
Collecting pep517
Using cached pep517-0.10.0-py2.py3-none-any.whl (19 kB)
Collecting toml
Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Installing collected packages: click, pip, toml, pep517, pip-tools
Attempting uninstall: pip
Found existing installation: pip 20.1.1
Uninstalling pip-20.1.1:
Successfully uninstalled pip-20.1.1
Successfully installed click-8.0.1 pep517-0.10.0 pip-21.1.2 pip-tools-6.1.0 toml-0.10.2
(test) molpopgen@pop-os:/venvs$ pip-compile requirements.txt
Could not find a version that matches markdown-it-py~=0.6.0,~=0.6.2,~=1.0 (from jupytext==1.10.3->jupyter-book==0.11.1->-r requirements.txt (line 1))
Tried: 0.1.0, 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6, 0.4.7, 0.4.7, 0.4.8, 0.4.8, 0.4.9, 0.4.9, 0.5.0, 0.5.0, 0.5.1, 0.5.1, 0.5.2, 0.5.2, 0.5.3, 0.5.3, 0.5.4, 0.5.4, 0.5.5, 0.5.5, 0.5.6, 0.5.6, 0.5.7, 0.5.7, 0.5.8, 0.5.8, 0.6.0, 0.6.0, 0.6.1, 0.6.1, 0.6.2, 0.6.2, 1.0.0, 1.0.0, 1.1.0, 1.1.0
Skipped pre-versions: 1.0.0b1, 1.0.0b1, 1.0.0b2, 1.0.0b2, 1.0.0b3, 1.0.0b3
There are incompatible versions in the resolved dependencies:
markdown-it-py~=0.6.2 (from myst-parser==0.13.7->myst-nb==0.12.3->jupyter-book==0.11.1->-r requirements.txt (line 1))
markdown-it-py~=1.0 (from mdit-py-plugins==0.2.8->myst-parser==0.13.7->myst-nb==0.12.3->jupyter-book==0.11.1->-r requirements.txt (line 1))
markdown-it-py~=0.6.0 (from jupytext==1.10.3->jupyter-book==0.11.1->-r requirements.txt (line 1))
Expected behavior
I expected a consistent set of pinned dependencies that I could store in a requirements.txt file.
Environment
Python 3.8.6 on Pop OS 20.04
Issue Analytics
- State:
- Created 2 years ago
- Comments:37 (20 by maintainers)
Top Results From Across the Web
jupyter-book - PyPI
Jupyter Book is an open-source tool for building publication-quality books and documents from computational material. using a simple command, run the embedded ...
Read more >Overview - Jupyter Book
Create your book's content. You structure your book with a collection of folders, files, and configuration. · Build your book. Using Jupyter Book's...
Read more >What does the error message about pip --use-feature=2020 ...
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it ......
Read more >jupyter-book vulnerabilities | Snyk
Learn more about known vulnerabilities in the jupyter-book package. Build a book with Jupyter Notebooks and Sphinx.
Read more >Jupyter and the future of IPython — IPython
IPython provides a rich architecture for interactive computing with: ... Book: Cyrille Rossant has published the second edition of the IPython minibook: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
well, as you can see lol, its also frustrating for me, since I have gone to great pains to ensure all the dependency pieces fit together 🥴. But yeh come v0.12, this should all clear up, and then the point of releasing markdown-it-py v1 was that it should be pretty stable now and rarely incur any further breaking changes.
Just FYI, this problem also arises when using pipenv to manage a project’s environment. I have worked around it with direct, restricted dependency on
mdit-py-plugins
: