-
Notifications
You must be signed in to change notification settings - Fork 292
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
Got dependency issue with spacy and markupsafe #1269
Comments
Strictly speaking, this is not dependency issue with spacy/markupsafe, but jinja2 and markupsafe. I am okay to pin the markupsafe package version to 2.0.1. It is weird that this error escaped our CI test though: |
@xwang233 Is it because the jinja2 version in your local docker is old? The latest 3.1.x version doesn't import |
It could be the reason. Our CI is using |
@xwang233 imo we should pin |
@xwang233 just want to confirm, are you going to submit a PR? |
Hi @xuzhao9 , I won't submit a PR about this since it's not an upstream issue but actually an issue in our environment. I'll fix our environment instead. |
Closed as this is downstream environment issue. |
After this PR #1261 change 94078d9#diff-fcf1c48cd82709b9bd6dc7881e2a425d15502a75925097be18583a7c6a0ffdafR5, while doing
python install.py
, I gotThere is a similar issue aws/aws-sam-cli#3661 (comment).
My temporary workaround is to pin the package version
markupsafe==2.0.1
like thisxwang233@3dcf675
cc @xuzhao9
The text was updated successfully, but these errors were encountered: