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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you meant
lxml >= 4.9.0
orlxml ~= 4.9
or simplylxml
? It makes no sense to allow 4.9.0 but disallow 4.9.1.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am adding pin to avoid any breaking change in any upcoming release. Just update the pin as per new release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pinning the version like this does not work well for projects using
python3-saml
. In order for a project to updatelxml
for a security update you have to wait for a new release ofpython3-saml
. It is a trade off between ensuring that the specified version works and allowing flexibility for users. Ideally we would assume that future versions oflxml
work correctly, and make a patch release rejecting certain releases if an issue is identified.