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

Dependencies: put upper limit markupsafe<2.1 #5371

Merged
merged 1 commit into from
Feb 21, 2022

Conversation

sphuber
Copy link
Contributor

@sphuber sphuber commented Feb 21, 2022

Fixes #5367

The latest release markupsafe==2.1 breaks jinja<3.0 and that in
turn breaks sphinx<4.0. Upgrading to sphinx~=4.0 brings its own
problems with a whole host of new warnings that cannot be easily fixed
and so instead we are putting an upper limit on markupsafe.

The latest release `markupsafe==2.1` breaks `jinja<3.0` and that in
turn breaks `sphinx<4.0`. Upgrading to `sphinx~=4.0` brings its own
problems with a whole host of new warnings that cannot be easily fixed
and so instead we are putting an upper limit on `markupsafe`.
@sphuber
Copy link
Contributor Author

sphuber commented Feb 21, 2022

I originally tried to fix this issue in #5369 by just upping all involved dependencies (dependency chain is sphinx -> jinja -> markupsafe) but to do so we need sphinx>=4.0 which comes with a host of other problems that are not trivial to fix for now, so we will have to leave that for another time.

@sphuber sphuber merged commit 139f7d2 into aiidateam:develop Feb 21, 2022
@sphuber sphuber deleted the fix/docs-build branch February 21, 2022 17:16
sphuber added a commit that referenced this pull request Mar 7, 2022
The latest release `markupsafe==2.1` breaks `jinja<3.0` and that in
turn breaks `sphinx<4.0`. Upgrading to `sphinx~=4.0` brings its own
problems with a whole host of new warnings that cannot be easily fixed
and so instead we are putting an upper limit on `markupsafe`.

Cherry-pick: 139f7d2
sphuber added a commit that referenced this pull request Mar 7, 2022
The latest release `markupsafe==2.1` breaks `jinja<3.0` and that in
turn breaks `sphinx<4.0`. Upgrading to `sphinx~=4.0` brings its own
problems with a whole host of new warnings that cannot be easily fixed
and so instead we are putting an upper limit on `markupsafe`.

Cherry-pick: 139f7d2
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 this pull request may close these issues.

readthedocs build failing
2 participants