Closed Li-Xiang-Ideal closed 8 months ago
Thank you!
I’ve simplified the code a little bit and used a specific environment variable called CAIROCFFI_DLL_DIRECTORIES
instead of PATH
(because the use of PATH
was removed on purpose).
I’ve also updated the documentation.
Hi, is there a timeline for when this fix might see a release? If I understand correctly, this fixes something for Windows users that was introduced in Python 3.8, so a fair while back. I guess people must have been working around this themselves? Would be nice if there was a canonical way of addressing this.
A new version has been released.
Thanks for releasing this. It works for me when adding the new environment variable. However, I am puzzled how a change introduced in Python 3.8 has these repercussions only now?
However, I am puzzled how a change introduced in Python 3.8 has these repercussions only now?
Almost all CairoCFFI users are on Linux, I suppose that’s why.
And many on Windows are using WSL or MSYS2? Just found this evening that using Python on MSYS2 just works with just the Path set. Thanks for the info.
And many on Windows are using WSL or MSYS2? Just found this evening that using Python on MSYS2 just works with just the Path set. Thanks for the info.
Yes, MSYS2 is a great way to get DLLs easily installed, maintained and usable on Windows.
A new version has been released.
new release? do you mean cairocffi 171? i upgraded to 171 and issue still.. i'm on windows 10 OSError: no library called "cairo-2" was found
new release? do you mean cairocffi 171?
Yes (actually, even 1.7.0).
Did you set CAIROCFFI_DLL_DIRECTORIES
as explained in this PR and in the documentation?
Python 3.8+ no longer searches for DLLs in PATH. Add paths in PATH manually. See PyCairo Windows Python3.8 Import Issue