feat: Allow lxml 5.x and require python >= 3.8 #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JennToo
approved these changes
Feb 7, 2024
|
Thanks Andrew! |
|
Released in 3.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #29
lxml 5.x has been released and available for about a month now, so I increased the range of allowed lxml versions to include 5.x and then regenerated the lock file.
I also took the liberty of increasing the minimum supported python version to 3.8, which is the oldest non-EOL version as of today. I bumped the minor version to 2.6.0. If this needs to be a major rev instead, let me know.
Tests passed locally in a python 3.12 environment.