I'm working on tools to convert python packaging data to rpm spec
files. Most of the conversions are relatively straightforward, but
there's an odd corner case with ">" and versions ending in ".*". That
combination is parsed as a valid specification, but oddly, it seems to
behave the same as ">= version", as demonstrated below. Is this
intentional, or is it a byproduct of parsing ">1.0.*" as a
LegacySpecifier?
Should I convert ">1.0.*" into ">=1.0" and mimic the current behavior,
or into something else, like "> 1.0", or ">= 1.1"?
>>> pkg_resources._vendor.packaging.requirements.Requirement('cairocffi >
>>> 1.0.*,< 1.0.1').specifier._specs
frozenset({<LegacySpecifier('>1.0.*')>, <Specifier('<1.0.1')>})
>>> '1.7' in pkg_resources.Requirement.parse('foo>1.7.*')
True
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
https://mail.python.org/mailman3/lists/distutils-sig.python.org/
Message archived at
https://mail.python.org/archives/list/distutils-sig@python.org/message/NWEQVTCX5CR2RKW2LT4H77PJTEINSX7P/
