Upper bound for markupsafe dependency #19753
|
Overview Currently Jinja2 upper bound is Jinja2 seems to require Based on this, is it feasible to consider updating upper bound in airflow for IssueI am facing a dependency conflict(using poetry) where one of the libraries I am using requires Please share your thoughts as I may be missing some context/rationale behind not doing this. There could be compatibility issues which I may not be aware of. I am just looking at the dependency chain and have not tried this change myself yet. I thought to ask here first in case this has already been discussed or if there are risks with doing this change. Are you willing to submit a PR?If there is a consensus on suggested change, then I can contribute the change. I will need to review the process and will require some guidance. |
Replies: 1 comment 5 replies
|
You can try remove the limit. Unfortunately markupsafe 2.0 limit is not commented and it's been moved here from setup.py and it has long history - tracing the origin of that limit might be difficult. However I think this was just a 'safeguard' in case of future incompatibilities. Which we stopped doing pretty much. We have constraints mechanism that allows us to safeguard against future-backwards-incompatible releases, and we tend to update all the dependencies to remove all the "upper-bound" limits (unless they are needed - then we leave a comment there why). However - I have a bad news for you - you will lilkely have different problems with poetry - because it does not support constraints, so the bad news for you is that the only supported installation method for airflow is Just to repeat again - installing with And If you want you can see my talk from today where I explained why we have this: https://www.youtube.com/watch?v=_SjMdQLP30s&t=2549s , also you can see the issue that wes closed by poetry maintainer with the comment that they won't add support for constratints python-poetry/poetry#3225 What you can try to do is I think you can try to remove the upper bounds and make a PR - it will automatically try to upgrade to latest dependencies which "comply" with other limtis and will run tests for them. If those tests pass, we should be able to merge the PR and get rid of the upper bound (but it will not solve the underlying problems that trying to use poetry to install airflow consistently will not work until they support constraints). Just be aware that there might other dependencies that might hold Jinja2 from upgrding |
You can try remove the limit.
Unfortunately markupsafe 2.0 limit is not commented and it's been moved here from setup.py and it has long history - tracing the origin of that limit might be difficult.
However I think this was just a 'safeguard' in case of future incompatibilities. Which we stopped doing pretty much. We have constraints mechanism that allows us to safeguard against future-backwards-incompatible releases, and we tend to update all the dependencies to remove all the "upper-bound" limits (unless they are needed - then we leave a comment there why).
However - I have a bad news for you - you will lilkely have different problems with poetry - because it does not support constrain…