Latest version of MarkupSafe doesn't work with Great Expectations

[krishnasism]

Describe the bug
When importing great-expectations with the latest version, there's an issue with MarkupSafe. MarkupSafe latest version removes soft_unicode, which gx uses - thus resulting in the error cannot import name 'soft_unicode' from 'markupsafe'

To Reproduce
Install latest version of gx, and import great_expectations

Expected behavior
import should not fail

Environment (please complete the following information):

• Operating System: Linux
• Great Expectations Version: 1.3.2
• Cloud environment: Databricks
• Python version: 3.10

Comments
Please set a constraint in your pyproject for MarkupSafe>=2 (or whatever works) and MarkupSafe <3

[dctalbot]

Hi, thank you for reporting this issue. I'll share my investigation below:

(.venv) ➜ python --version
Python 3.10.14
(.venv) ➜ pip --version
pip 25.0.1
(.venv) ➜ pip install --no-cache-dir great-expectations==1.3.5
(.venv) ➜ pip freeze | grep MarkupSafe
MarkupSafe==3.0.2
(.venv) ➜ pip install pipdeptree
(.venv) ➜ pipdeptree -r -p markupsafe
MarkupSafe==3.0.2
└── Jinja2==3.1.5 [requires: MarkupSafe>=2.0]
    ├── altair==4.2.2 [requires: Jinja2]
    │   └── great-expectations==1.3.5 [requires: altair>=4.2.1,<5.0.0]
    └── great-expectations==1.3.5 [requires: Jinja2>=2.10]

---

• MarkupSafe is a sub-dependency via Jinja2.
• Unfortunately, MarkupSafe does not adhere to semantic versioning, so it is unclear when it will break
• They broke it here: remove deprecated code pallets/markupsafe#261
• Lots of complaints here: ImportError: cannot import name 'soft_unicode' from 'markupsafe' pallets/jinja#1585

---

• Based on other issues in github, the most likely problem in your environment is an incompatibility with Jinja2 < 3 and MarkupSafe >= 2.1

• If you have more information to share about your environment, such as the output of pip freeze, that may be helpful to inform our solution

• Is there something in your environment that is preventing you from upgrading to Jinja2 > 3?

• It's not clear to me yet whether adding a constraint on MarkupSafe is the right course of action, versus dropping support for Jinja2 < 3

[krishnasism]

I will try upgrading Jinja and let you know on a weekday. Let me know if you require any other information, I will try to share my pip freeze output as well. I am installing it in a Databricks environment. Will send you more information.

[dctalbot]

Thanks, that would be greatly appreciated! Our team decided to drop support for Jinja2 v2 regardless. I've marked this issue as resolved since that is likely the source of this error. However, please let us know if your issue persists for any other reason.