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
Backport: add locked requirements #6253
Backport: add locked requirements #6253
Conversation
I'll debug this tomorrow morning |
https://pip.pypa.io/en/stable/news/#id13 pip 22.0 dropped support for Python 3.6. What should we do? Should we lock an old version of pip? Should we drop Python 3.6? It might be possible to make the lock depend on the python version. |
Lock pip to a working version. In 1.1-maint, we should not drop old python versions except if there is no other possibility or if they are out of support for a while. And use same pip for all py versions, so that we do not get different behavior just because of that. |
5a8050a
to
ed75589
Compare
Codecov Report
@@ Coverage Diff @@
## 1.1-maint #6253 +/- ##
=============================================
- Coverage 79.69% 79.68% -0.01%
=============================================
Files 27 27
Lines 10494 10494
Branches 2149 2149
=============================================
- Hits 8363 8362 -1
- Misses 1605 1606 +1
Partials 526 526
Continue to review full report at Codecov.
|
79d60b4
to
1ee72e1
Compare
AttributeError: module 'collections' has no attribute 'MutableMapping I'll debug this later today |
Possibly relevant: pytest-dev/pytest#8539 pytest-dev/pytest#8546 |
I have tried the existing requirements.d/development.lock.txt and it fails on python3.10 too. There appears to be no version of pytest that simultaneously supports both py3.5 ad 3.10:
I see two paths forward:
|
just noticed that i used the locked requirements for the "main" borg build in vagrant (see Vagrantfile). but then, when tox runs in the vagrant machine, it uses the unlocked requirements (see tox.ini). so, we'll just ignore the py310 issue and make the locked requirements as good as it gets for < 3.10. note: the borg binaries are built with python 3.7.11 so it is most important to have everything up-to-date that is used for that. |
This appears to be at odds with the goal of supporting 3.5: $ python -V
Python 3.7.11
$ pip list --outdated
Package Version Latest Type
-------------- ------- ------ -----
pip 20.3.4 22.0.3 wheel
pluggy 0.13.1 1.0.0 wheel
pytest 6.1.2 7.0.0 wheel
pytest-cov 2.12.1 3.0.0 wheel
pytest-xdist 2.2.1 2.5.0 wheel
setuptools 50.3.2 60.8.1 wheel
setuptools-scm 5.0.2 6.4.2 wheel
twine 1.15.0 3.8.0 wheel
|
When I said "up-to-date" I meant also "as good as it gets" considering our other requirements (thus not necessarily using the latest and greatest, but something more recent than we had before). |
BTW, considering your recent activity, feel free to add yourself to AUTHORS file if you like. |
Should be ready now. CI is happy with the locks: https://github.com/borgbackup/borg/runs/5085767052 |
This will be a backport of #6235
Fixes: #6224
The first step is to test the updated requirements on github ci. I'll add the rest once the CI is green.
#6235 (comment)