-
-
Notifications
You must be signed in to change notification settings - Fork 698
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
Perhaps a simple question, but which version was flexbox support implemented in? #658
Comments
For additional context, this (as well as my personal examples) renders properly in browser |
@gaoag I hit this exact problem right around the moment you posted this issue. I was able to get everything working by updating the library to the latest version on the master branch, so it looks like those changes haven't been published yet. I'm rather new to WeasyPrint so I'm not entirely sure of the stability of the master branch, but I can confirm that everything seems to be running fine with flexbox support. |
Thanks @JenkinsDev . Mind telling me how you updated the library? Did you simply replace all the files in the 'weasyprint' folder of your python packages with the files in the master branch? |
Flexbox support is only in Next release will include a lot of CSS features (flexbox, named strings…), drops Python 2 support and improves speed. It will probably be ready during September. Follow the 43 milestone to know what's going on! (And if you would like to discuss the next features of your dreams, please add a comment to #635, I'll be glad to make WeasyPrint fit your needs!) |
@gaoag Remove any previous versions you have installed, then install with |
For anybody that tries @JenkinsDev's solution above and receives the following error:
Try running |
Hi,
I have the latest WeasyPrint version from pip (0.42.3), but I do not believe it has flexbox support. I tried the minimal example provided at #613 and it indicated
How am I supposed to install the version of WeasyPrint that has flexbox support, as referenced in #579 ?
The text was updated successfully, but these errors were encountered: