-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
MarkupSafe on 2.1.0 breaks Jinja #1590
Comments
Duplicate of #1585 Please read https://hynek.me/articles/semver-will-not-save-you/, then use a tool like pip-tools to pin your dependencies and control when you get updates. |
Erm, your source depends on |
Duplicate of #1585 You are using an unsupported version of the project, please update to the latest version. Additionally, please read https://hynek.me/articles/semver-will-not-save-you/, then use a tool like pip-tools to pin your dependencies and control when you get updates. Be sure to run your tests with deprecation warnings treated as errors so that you get notified of these types of changes early. |
Ah damn, you are right, sorry. "Fault" is on Lintly then, will open a ticket there. Although, it might have been nice if you pinned your versions yourself in earlier versions, then outdating would not have been an issue and the unsupported version would not necessitate using |
The dependency of MarkupSafe just says >=2 but this breaks with the recent update to Jinja.
I stumbled upon it by using Lintly that depends on Jinja2.
Edit: changed log, had the wrong one
The text was updated successfully, but these errors were encountered: