Skip to content
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

Unpinned WeasyPrint to allow Addon to use newer version #838

Merged
merged 3 commits into from
May 22, 2018

Conversation

ramonski
Copy link
Contributor

Description of the issue/feature this PR addresses

WeasyPrint is currently pinned to 0.42.2. It is not possible for Add-ons to use e.g. 0.42.3 because of that version constraint.

Anyhow, we should go with the latest versions of WeasyPrint...

Current behavior before PR

WeasyPrint pinned to 0.42.2

Desired behavior after PR is merged

WeasyPrint unpinned. Newest version is fetched (currently 0.42.3)

--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.

Copy link
Member

@xispa xispa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, add a comment like "This update requires the execution of bin/buildout, because ..." in RELEASE_NOTES.rst. See update 1.2.3 to 1.2.4 https://github.com/senaite/senaite.core/blob/master/RELEASE_NOTES.rst#update-from-123-to-124

@ramonski
Copy link
Contributor Author

I thought about that as well, but I think most of the people should be fine with 0.42.2. So unless 0.42.3 or any greater version gives us a real advantage over any older version, I would keep that change silently...

@xispa
Copy link
Member

xispa commented May 22, 2018

Understand, ssince we don't add anything in the code that depends on the new version of weasyprint. then no need to warn the user for something that will not have any impact. Accepting.

@xispa xispa merged commit 5cd022e into master May 22, 2018
@xispa xispa deleted the unpin-weasyprint branch May 22, 2018 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants