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
I'm using Pillow as a transient dependency of matplotlib inside a Nix Flake which uses poetry2nix.
Pillow updated from 9.4.0 to 9.5.0 because of matplotlib's loose specification.
What did you expect to happen?
Transparent update. Rebuild & move on.
What actually happened?
Pillow 9.5.0 fails to find zlib when building.
What are your OS, Python and Pillow versions?
OS: macOS 13.3.1 (a) - but Nix is the more relevant point here
04cf5e2 broke this usage pattern, because in this case it will now iterate over each string's characters and add them as lib/include paths.
It looks to me that this bug is already resolved by fe4e52d , which is not yet released. The commit message reads like a refactor, so @radarhere I'm not sure if you've spotted that there is actually a functional change?
So, if that commit goes out on the next release everything is fine, but right now 9.5.0 is broken with any system which assigns the (lib_root, include_root) tuple pattern to the ${LIB}_ROOT globals.
The text was updated successfully, but these errors were encountered:
What did you do?
I'm using Pillow as a transient dependency of matplotlib inside a Nix Flake which uses poetry2nix.
Pillow updated from 9.4.0 to 9.5.0 because of matplotlib's loose specification.
What did you expect to happen?
Transparent update. Rebuild & move on.
What actually happened?
Pillow 9.5.0 fails to find zlib when building.
What are your OS, Python and Pillow versions?
This is how Nix injects the correct paths to the native dependencies: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/python-modules/pillow/generic.nix#L59
So, Pillow's setup.py ends up looking like:
setup.py L471 effectively sets:
04cf5e2 broke this usage pattern, because in this case it will now iterate over each string's characters and add them as lib/include paths.
It looks to me that this bug is already resolved by fe4e52d , which is not yet released. The commit message reads like a refactor, so @radarhere I'm not sure if you've spotted that there is actually a functional change?
So, if that commit goes out on the next release everything is fine, but right now 9.5.0 is broken with any system which assigns the (lib_root, include_root) tuple pattern to the ${LIB}_ROOT globals.
The text was updated successfully, but these errors were encountered: