You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Putting this issue here in case other people run into the same error. It's fixable by pulling the new version of rootstock, but that isn't obvious from the build error message
The people who develop Markupsafe pushed a breaking change that causes old versions of Jinja2 to break unless you manually pin an old version of Markupsafe to work around it. The official line seems to be "it's your fault for not updating Jinja", so I imagine there isn't a fix coming.
Again, this isn't an issue with the live version of rootstock, but does break builds for anyone who hasn't updated rootstock since December
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out @ben-heil. I'm adding the text of the error message to help anyone who searches for a solution.
ImportError: cannot import name 'soft_unicode' from 'markupsafe' (/usr/share/miniconda3/envs/manubot/lib/python3.7/site-packages/markupsafe/__init__.py)
If this is a widespread problem, we can pin this issue to make it easier to find.
dcsoto
pushed a commit
to computer-aided-biotech/better-cb
that referenced
this issue
Feb 25, 2022
New version of Markup safe breaks with old Jinja version. To work around it, an older version of Markupsafe needs to be manually added (manubot/rootstock#459). I added version 2.0.1 to the environment YAML (pallets/markupsafe#284).
Putting this issue here in case other people run into the same error. It's fixable by pulling the new version of rootstock, but that isn't obvious from the build error message
The people who develop Markupsafe pushed a breaking change that causes old versions of Jinja2 to break unless you manually pin an old version of Markupsafe to work around it. The official line seems to be "it's your fault for not updating Jinja", so I imagine there isn't a fix coming.
Again, this isn't an issue with the live version of rootstock, but does break builds for anyone who hasn't updated rootstock since December
The text was updated successfully, but these errors were encountered: