-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: fix the CI failures on packaging > 22 #115
Conversation
Python 2.7 is failing due to incompatible |
What's the solution for those that don't have the option to stay with the old version? |
That is the test dependency and resolvelib itself doesn't have any dependency |
Right, but the environment I'm looking at (Debian Testing) has the newer version, so running the tests with the older version isn't an option. Maybe put the relevant tests inside try/except and then pass on that error from packaging so testing with the newer version at least doesn't cause inappropriate test failures?
Scott K
|
The Swift tests actually implement a hand-rolled extremely simplified parser, perhaps we could do the same? https://github.com/sarugaku/resolvelib/blob/master/tests/functional/swift-package-manager/test_resolvers_swift.py |
Because there are test cases against indexes for other languages and their version don't follow the python standards,
we have to set version cap of packaging to<22.0
for testing.Also, switch to
nox
in CI workflows.Fixes #114