Fix dependencies for Python 3.7 or drop support for it #784
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#784
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Currently, Python 3.7 will fail because some dependencies have dropped support for it.
We'd either need to drop support for it as well or pin dependencies to functioning versions just for Python 3.7.
Steps to reproduce
tox
Actual behavior
In the
py37
environment:Expected behavior
Tests run without errors on all environments.
Other notes / implementation ideas
Drop Python 3.7. It's been EOL for over 3 years.
borgmatic version
12b75f9075
borgmatic installation method
No response
Borg version
No response
Python version
No response
Database version (if applicable)
No response
Operating system and version
No response
Thanks for taking the time to file this one! I've actually been itching for an excuse to drop support for Python 3.7, and this is as good as any. I'll note that that 3.7 security support has only been EOL for a few months at this point. But that's good enough for me! We don't have infinite resources to support all versions of Python for all time.
Implemented in main. Will be part of the next release. Thanks again!
Just released with borgmatic 1.8.5!