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

HTML() to accept pathlib.Path object #622

prehensilecode opened this issue Apr 25, 2018 · 1 comment

HTML() to accept pathlib.Path object #622

prehensilecode opened this issue Apr 25, 2018 · 1 comment


Copy link

@prehensilecode prehensilecode commented Apr 25, 2018

I would like to request that weasyprint.HTML() accepts a pathlib.Path object

#!/usr/bin/env python3
import sys
import os
import pathlib
import weasyprint

### this works
pdfbytes = weasyprint.HTML('foobar.html')

### writing with Path object works
pdffile = pathlib.Path('./foobar2.pdf')

### this does not
pdfbytes = weasyprint.HTML('./foobar.html')

### this does not
htmlfile = pathlib.Path('./foobar.html')
pdfbytes = weasyprint.HTML(htmlfile)
@liZe liZe changed the title Feature request - HTML() to accept pathlib.Path object HTML() to accept pathlib.Path object Apr 26, 2018
@liZe liZe added this to the 43 milestone Aug 17, 2018
@liZe liZe closed this in 1dbe26a Aug 21, 2018
Copy link

@liZe liZe commented Aug 21, 2018

Thanks for the idea!

It's fixed in current master branch and should work with CSS and Attachment instances as well.

Just to be sure: the pdfbytes = weasyprint.HTML('./foobar.html') example works for me, as long as foobar.html is in the current folder. Is it really broken for you?

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Nov 14, 2018
Version 43

Released on 2018-11-09.

Bug fixes:

* `#726 <>`_:
  Make empty strings clear previous values of named strings
* `#729 <>`_:
  Include tools in packaging

This version also includes the changes from unstable rc1 and rc2 versions
listed below.

Version 43rc2

Released on 2018-11-02.

**This version is experimental, don't use it in production. If you find bugs,
please report them!**

Bug fixes:

* `#706 <>`_:
  Fix text-indent at the beginning of a page
* `#687 <>`_:
  Allow query strings in file:// URIs
* `#720 <>`_:
  Optimize minimum size calculation of long inline elements
* `#717 <>`_:
  Display <details> tags as blocks
* `#691 <>`_:
  Don't recalculate max content widths when distributing extra space for tables
* `#722 <>`_:
  Fix bookmarks and strings set on images
* `#723 <>`_:
  Warn users when string() is not used in page margin

Version 43rc1

Released on 2018-10-15.

**This version is experimental, don't use it in production. If you find bugs,
please report them!**


* Python 3.4+ is now needed, Python 2.x is not supported anymore
* Cairo 1.15.4+ is now needed, but 1.10+ should work with missing features
  (such as links, outlines and metadata)
* Pdfrw is not needed anymore

New features:

* `Beautiful website <>`_
* `#579 <>`_:
  Initial support of flexbox
* `#592 <>`_:
  Support @font-face on Windows
* `#306 <>`_:
  Add a timeout parameter to the URL fetcher functions
* `#594 <>`_:
  Split tests using modern pytest features
* `#599 <>`_:
  Make tests pass on Windows
* `#604 <>`_:
  Handle target counters and target texts
* `#631 <>`_:
  Enable counter-increment and counter-reset in page context
* `#622 <>`_:
  Allow pathlib.Path objects for HTML, CSS and Attachment classes
* `#674 <>`_:
  Add extensive installation instructions for Windows

Bug fixes:

* `#558 <>`_:
  Fix attachments
* `#565 <>`_,
  `#596 <>`_,
  `#539 <>`_:
  Fix many PDF rendering, printing and compatibility problems
* `#614 <>`_:
  Avoid crashes and endless loops caused by a Pango bug
* `#662 <>`_:
  Fix warnings and errors when generating documentation
* `#666 <>`_,
  `#685 <>`_:
  Fix many table layout rendering problems
* `#680 <>`_:
  Don't crash when there's no font available
* `#662 <>`_:
  Fix support of some align values in tables
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants