mirror of
git://git.yoctoproject.org/layerindex-web.git
synced 2025-07-05 05:04:46 +02:00
83378f2f9c
Since we are only using parse_version for comparison (typically checking that we are greater than some minimum version for tool or package), one would think we can use packaging.version.parse as if it was parse_version Unfortunately, this requires conforming to PEP-440 version definitions, which does not work for e.g. autotools (2.72d) nor older openssl (1.1.1p). We rely in these (and to be sure other) cases on the LegacyVersion behavior. https://packaging.python.org/en/latest/specifications/version-specifiers/#summary-of-differences-from-pkg-resources-parse-version "This specification purposely restricts the syntax which constitutes a valid version while pkg_resources.parse_version attempts to provide some meaning from any arbitrary string." In order to have the least impact to the overall code, we instead add packaging_legacy to requirements.txt and use packaging_legacy.version.parse as if it was parse_version. https://pypi.org/project/packaging-legacy/ https://github.com/pypa/packaging/pull/407 Since pypi.org itself is depending on packaging_legacy (in fact, a pypi dev developed the package), we can expect it to be supported for quite some time. https://github.com/pypi/warehouse/pull/13500 [YOCTO #15348] Signed-off-by: Tim Orling <tim.orling@konsulko.com> |
||
|---|---|---|
| .. | ||
| migrations | ||
| static | ||
| templatetags | ||
| tools | ||
| __init__.py | ||
| admin.py | ||
| auth_forms.py | ||
| auth_views.py | ||
| bulkchange.py | ||
| context_processors.py | ||
| forms.py | ||
| layerconfparse.py | ||
| middleware.py | ||
| models.py | ||
| querysethelper.py | ||
| recipedesc.py | ||
| recipeparse.py | ||
| restperm.py | ||
| restviews.py | ||
| securityquestions.py | ||
| tasks.py | ||
| update_layer.py | ||
| update.py | ||
| urls_branch.py | ||
| urls.py | ||
| utils.py | ||
| views.py | ||