-
-
Notifications
You must be signed in to change notification settings - Fork 688
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
v53.0b2 Global Installation #1384
Comments
Hello! WeasyPrint 53 requires at least Pango 1.44. You probably have an older version, that’s why you get this error. |
Thanks, but if I use |
You can get your version of Pango with |
I see, it's giving me Pango version 14203 for some reason. Will figure out why and get it to upgrade. Thanks for the help. |
After some digging, turns out it's that Debian’s repo does not include 1.44. Unable to get around this in a CI environment, sans waiting for the next Debian to be released. That having been said, I think it would be great if the new docs could show the steps required to get WeasyPrint up and running globally, outside of a virtual environment. Whilst virtual environments seem cool (note: this coming from a developer who does not develop in Python), it does mean that the binary path varies from environment to environment, and sometimes a constant global path might be required. Do you think this is something that could be added to the docs? |
Running into the same issue trying to get |
Then it’s probably time to find a workaround for Pango < 1.44. |
The workaround has been added, and will be removed when the next Debian stable version is released. Tests are welcome! Note that using Pango < 1.44 brings #1199 back. |
That’s broken, because we miss |
Hmmmm… I’m really sorry, but in my opinion there’s no way to replace Yes, that’s really annoying. We have Pango 1.44+ in the latest version of many distributions, and even in the latest Ubuntu LTS, but not in Debian stable or in CentOS. If someone is really motivated and knows Pango 1.42 very well, I would be interested in a dirty workaround, but unfortunately I’m not able to write this one myself. Otherwise, I’m afraid that distributions with Pango 1.42 will have to keep WeasyPrint 52.x :/. "Good" news is that Bullseye hit "full freeze" status yesterday. It’s the last step before the release, it took about 3.5 months for Buster and Stretch. I’m really open to discussion about this topic. |
Release date is 14 August, Debian users won’t have to wait for too long. CentOS / RHEL / AWS is another problem. The next dev version was announced for Q2 2021, but I didn’t find anything more than that. If anyone is interested in discussing this topic, it’s the last call. We’ve already updated the documentation to warn users about this problem. |
From my side, CI is using Debian, so I'm happy to wait it out. Thanks! :) |
Feel free to reopen if anyone thinks that this topic requires more discussion. |
WeasyPrint >= 53 requires pango 1.44 Kozea/WeasyPrint#1384
WeasyPrint >= 53 requires pango 1.44 Kozea/WeasyPrint#1384
I was using the official python docker images, which is based on buster, and hit this issue. |
Hello, we have recently ran into breaking changes with v53. We are running the application in a docker FROM PYTHON-3.8. The stacktrace is the following:
We believe the error is caused by v53 requiring pango >= 1.44.0 Our Dockerfile, which used to work with previous weasyprint versions, contains the following line: We are considering either downgrading back to weasyprint v52 or attempting to upgrade the pango version... What do you all recommend? |
That’s the cause of this problem.
You can wait for the next version of Debian stable (11, Bullseye), it’s expected to be released tomorrow and it includes a recent version of Pango. |
Thank you for such a quick response. We have gone ahead and downgraded weasyprint to v52. Everything is back to normal. On a side note, if we wait for Bullseye, will we have to change anything in the Dockerfile? Maybe remove this line completely?: |
You can find an updated list of required packages in the documentation. |
Currently facing the same issue while building python script on Jenkins. How can I mitigate the error? I've tried upgrading almost every library. |
Version 53 of WeasyPrint requires pango >= 1.44.0. |
Already done, yet I receive the same error. |
That’s strange, because |
My apologies, I had both weasyprint 53 and 52.5 installed. Removed the version 53, and it worked well.
|
@liZe Is there any work around found for AWS Lambda. I am trying to use weasyprint v53.1 with pango 1.48+ and I get the same error.
|
Hello! WeasyPrint 53 needs pango >= 1.44. As far as I know, the version of pango available on Amazon Linux 2 is 1.42. Maybe @kalekseev knows more about that? :) And I think it would be best to open a new issue about that, as this one is closed and is about the beta. |
Pinned layer to v52 for now https://github.com/kotify/cloud-print-utils/pull/7/files |
@kalekseev thanks for the help. Did the same as your pull suggests within my clone with added personal dependencies. Thanks again @kalekseev @grewn0uille . |
Just for the record. WeasyPrint 53.3 now working fine for me after using a Debian Bullseye based docker image. |
WeasyPrint >= 53 requires pango 1.44 Kozea/WeasyPrint#1384
Same issue on Mac with arm M1 WeasyPrint==55.0
|
@rrr3try As explained in the documentation, recent versions of WeasyPrint require Pango ≥ 1.44.0. Upgrade Pango or use an older version of WeasyPrint. |
Finally Got Weasyprint to work in AWS Lambda. ✅ |
Can you please help me with same issue? And pango-view --version gives me: I tried to update pango to >= 1.44 but failed to do it, can you please help me how to install higher version of pango? |
Debian Buster provides Pango 1.42.3. If you want a more recent version of Pango, you’ll need a more recent of Debian: use the |
wow, thank you, now I fixed it! |
How do I install this version globally (outside of a virtual environment)? I'm attempting to get this done in a GitLab CI script, and am battling with dependencies and errors.
My CI script is on a php:8 image as the package is for PHP and needs to be tested.
I've arrived at a point where the dependencies seem correct, but am now getting this error:
These are the dependencies (some for PHP):
Many thanks!
The text was updated successfully, but these errors were encountered: