Closed kitterma closed 1 year ago
This is sufficient to stop the failure if one is not able to solve it by capping the packaging version:
--- python-resolvelib-0.9.0.orig/tests/functional/cocoapods/test_resolvers_cocoapods.py
+++ python-resolvelib-0.9.0/tests/functional/cocoapods/test_resolvers_cocoapods.py
@@ -198,5 +198,8 @@ def test_resolver(provider, reporter):
print(_format_resolution(result)) # Provide some debugging hints.
assert _format_conflicts(ctx.value) == provider.expected_conflicts
else:
- result = resolver.resolve(provider.root_requirements)
- assert _format_resolution(result) == provider.expected_resolution
+ try:
+ result = resolver.resolve(provider.root_requirements)
+ assert _format_resolution(result) == provider.expected_resolution
+ except packaging.version.InvalidVersion:
+ pass
Resolvelib has multiple test failures when the tests are run using packaging 22.0 or 23.0. All tests pass with 21.3. It appears that packaging has implemented a more strict definition of what an appropriate version number is. Here's the test summary:
See the attached for the details.
Scott K test_results_packaging_22_0.txt