-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
Update markupsafe to 2.1.1, jinja2 to 3.1.2 #31937
Comments
comment:1
|
Author: Matthias Koeppe |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:5
LGTM. Thanks |
Reviewer: Isuru Fernando |
comment:7
Thanks! |
comment:8
I'm getting lots of
|
comment:9
Looks like this needs to wait for the sphinx update in #31696 |
Dependencies: #31696 |
comment:11
Setting a new milestone for this ticket based on a cursory review. |
This comment has been minimized.
This comment has been minimized.
Changed dependencies from #32518 to none |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:22
LGTM |
Changed reviewer from Isuru Fernando to Isuru Fernando, François Bissey |
comment:23
Thanks! |
Changed branch from u/mkoeppe/update_markupsafe_to_2_0_1 to |
Getting this warning with
markupsafe
2.0.1The new versions:
still support Python 3.7, so this update would even be safe for Sage 9.6
CC: @slel @antonio-rojas @kiwifb @egourgoulhon
Component: packages: standard
Author: Matthias Koeppe
Branch/Commit:
037fc2f
Reviewer: Isuru Fernando, François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/31937
The text was updated successfully, but these errors were encountered: