-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[24.0] Set minimum weasyprint version #18606
[24.0] Set minimum weasyprint version #18606
Conversation
We're not pinning transitive conditional dependencies, and a new pydyf version, which is a dependency of weasyprint, had a new release with a breaking change, see (Kozea/WeasyPrint#2200). Newer releases of weasyprint have introduced max version pins, so I think we're ok with just setting a minimum version here.
Arg, of course, that's why the tests failed. The fixed version is only available for python >= 3.9 ... . Guess we need some python version-specific logic here to pin the version of pydyf. |
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.
This fixes the API and Selenium tests, which run on Python 3.8, but I think this is still an issue for >=3.9. We will need to revisit this once a new Weasyprint release is out that includes Kozea/WeasyPrint@c345629 .
That commit just adds the upper bound, to make 3.9 work all that's needed is a recent version of weasyprint. |
I don't think this works with our custom parsing, but worth a try. Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
We're not pinning transitive conditional dependencies, and a new pydyf version, which is a dependency of weasyprint, had a new release with a breaking change, see (Kozea/WeasyPrint#2200).
Newer releases of weasyprint have introduced max version pins, so I think we're ok with just setting a minimum version here.
How to test the changes?
(Select all options that apply)
License