well, upstream dropped it here: https://github.com/pallets/markupsafe/pull/262/files so theoretically the change is wrong. however it appears no actual breakage with 3.6 was introduced

Anonymous User (_nobody_) - almost 2 years ago

This comment has been deleted

---

Dirk Mueller (dirkmueller) - almost 2 years ago

target maintainer

well, SLE/Leap 15 is still the more popular option over tumbleweed, so yes, some solution for the majority of users is warranted.

unless anyone objects I'd accept the SR.

I’m not sure this is a good idea. Upstream changed package metadata to require Python 3.7.

They are now free to change the code in any way such that it breaks at runtime on Python 3.6 and they could have done it between that commit and the release. At least we run tests, so I don’t have a strong opinion on whether that should prevent us from building it with Python 3.6.

/usr/lib64/python3.6/site-packages/MarkupSafe-2.1.1-py3.6.egg-info/PKG-INFO still contains Requires-Python: >=3.7. Therefore installing any package depending on it with pip will fail. For example:

Collecting Jinja2
  Using cached Jinja2-3.0.3-py3-none-any.whl (133 kB)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/lib64/python3.6/site-packages (from Jinja2) (2.1.1)
ERROR: Package 'MarkupSafe' requires a different Python: 3.6.15 not in '>=3.7'

I think we should at least patch /usr/lib64/python3.6/site-packages/MarkupSafe-2.1.1-py3.6.egg-info/PKG-INFO to contain Requires-Python: >=3.6.

Manuel Jacob (mjacob) - almost 2 years ago

I added a request for the latter approach: https://build.opensuse.org/request/show/984778