You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, when I'm refreshing Python installation on Windows 10, I end up with issues attempting to get weasyprint to work, and it's only that some random step that resolves the issue and I just overlook what happened and continue my day. Today however, I wanted to document what has happened to me in order to make sure I know exactly what has happened and how to resolve the issue in the future. I've done this:
Installed Python 3.8.3 from Windows Store (Not from Python website).
Installed GTK3 (64-bit) binaries from repo mentioned in weasyprint docs.
You are right the problem is with spaces in the directory name.
Just download the gtk+ bundle from here,
unzip the file into a directory with no spaces, ( C:\gtk ) for example,
finally just add the bin directory of the folder you unzipped into your path variable.
Occasionally, when I'm refreshing Python installation on Windows 10, I end up with issues attempting to get
weasyprint
to work, and it's only that some random step that resolves the issue and I just overlook what happened and continue my day. Today however, I wanted to document what has happened to me in order to make sure I know exactly what has happened and how to resolve the issue in the future. I've done this:weasyprint
docs.weasyprint
.python -c 'import weasyprint'
.To understand what's going on, I added a
breakpoint
at line 45 for file__init__.py
which is one step before raisingOSError
.Printing
exceptions
from the breakpoint gave the following message:I could be wrong, but isn't this asserting
ffi.dlopen
is failing because it's not correctly escaping the spaces in the path to load the lib?The text was updated successfully, but these errors were encountered: