Closed xwang233 closed 2 years ago
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 soft_unicode
from markupsafe
: https://github.com/pallets/jinja/blob/main/src/jinja2/filters.py#L13
It could be the reason. Our CI is using jinja2==2.11.3
. It could be pinned be another conda package in our environment.
@xwang233 imo we should pin jinja2
version here instead of markupsafe version. I can review a PR on that.
@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 https://github.com/pytorch/benchmark/pull/1261 change https://github.com/pytorch/benchmark/commit/94078d9288ff99ef50557a3bd87970badbef0458#diff-fcf1c48cd82709b9bd6dc7881e2a425d15502a75925097be18583a7c6a0ffdafR5, while doing
python install.py
, I gotThere is a similar issue https://github.com/aws/aws-sam-cli/issues/3661#issuecomment-1043965261.
My temporary workaround is to pin the package version
markupsafe==2.0.1
like this https://github.com/xwang233/benchmark/commit/3dcf675debbe5a6d55e23e15c95be9618fbf620ccc @xuzhao9