-
Notifications
You must be signed in to change notification settings - Fork 50
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
Problems pip installing pyvips 2.1.1 #33
Comments
only use vips_image_get_fields() on 8.5 and later thanks rebkwok see: https://github.com/jcupitt/pyvips/issues/33
Hello @rebkwok, Thanks for reporting this -- it was using vips_image_get_fields(), a feature only added in libvips 8.5. This used to work, since in ABI mode references are only looked up when they are used. In API mode (the new default in 2.1), all references are compiled at install time, so the undefined ref makes install fail. git master pyvips now tests the libvips version number before attempting to wrap vips_image_get_fields(). Would you be able to test it? Just clone the repo and install from there. |
I tried installing from the latest commit on master
But similar errors (although no reference to
|
there was a ref to parent_instance, which did not exist before libvips 8.4 see https://github.com/jcupitt/pyvips/issues/33
OK, fixed that too. Could you try again? I built and installed libvips 8.2 and it now works for me here. |
👍 All looking good here too. Thanks for the quick fix! |
woo, I'll push out an update. Thanks again! |
My install does:
A week ago this worked fine, and installed pyvips version 2.0.5 (libvips version 8.2.2-1) (Ubuntu 16.04, python 3.6)
However, now it is failing to install pyvips:
My libvips/libvips-dev versions are still 8.2.2-1, but the latest pypi pyvips version is 2.1.0.
pip install pyvips==2.0.5
works fine.The docs still say that pyvips just needs libvips > 8.2. Does the latest version of pyvips actually require a later version of libvips than 8.2.2-1 (which is the latest 16.04 debian package)
The text was updated successfully, but these errors were encountered: