John Cupitt

Oh dear, my fault, sorry. I'll try to think of a better fix for the chunking problem.

Maybe we should have another shrinkv path for factors > (just a guess) 100? Based on the older style of a row accumulator.

Hi @GuillaumeBalezo, `fetch` leaves the libvips pipeline open after it runs, so the next `fetch` operation doesn't need to rebuild everything. This helps latency for small regions, but it will...

I tried this: ```python #!/usr/bin/env python3 import sys import random import pyvips images = [pyvips.Image.new_from_file(filename, rgb=True) for filename in sys.argv[1:]] regions = [pyvips.Region.new(image) for image in images] #print(f"with fetch:") #for...

Hi @SteveHawk, pyvips works with any libvips version -- it introspects the libvips binary and exposes the API it finds. pyvips v2.2.1 should work fine with 8.15 and 8.16. Yes,...

Huh strange, it ought to work. I'll try to make a dockerfile for this. > Actually the package manager will download a LOT of dependencies (over 100 using conda, over...

> I installed pyvips with the prebuilt libvips-dev from [kleisauke/libvips-packaging](https://github.com/kleisauke/libvips-packaging) (with proper LD_LIBRARY_PATH and PKG_CONFIG_PATH set) and pip show reports the installation is using API mode. So I guess this...

I updated this dockerfile: https://github.com/jcupitt/docker-builds/blob/master/pyvips-alpine/Dockerfile And it seems to work fine. That's libvips 8.15.1 and pyvips 2.2.1 on alpine. I've not tried with those precompiled libvips binaries. If you need...

Ah that had popped out of my brain, thanks Kleis. Then I agree, a pyvips 2.2.2 would be useful. I'll do it now.

We might have v2.2.2, any testing very welcome.