search

uploadcare / pillow-simd

The friendly PIL fork
https://python-pillow.github.io/pillow-perf/
Other
2.18k stars 86 forks source link

10.1.0 version? #134

Open tot-ra opened 11 months ago

tot-ra commented 11 months ago

There were security vulnerabilities in pillow, so it got updates.. can you update to latest versions? pip shows 9.0 version as latest https://pypi.org/project/Pillow-SIMD/

time4tea commented 11 months ago

Hi pillow-simd maintainers - It would be amazing if you could make a release of this of version 10.x. This is now particularly being a problem as Pillow itself does not make wheels for pre-10 versions for windows, which is affecting Python 3.12 compatibility. Previously pillow-simd was a drop-in replacement for pillow, but now with various removed methods in pillow (particularly around text bounding boxes), but with pillow-simd being so far behind (textbbox changed behaviour in 9.2.0, but pillow-simd is at 9.0.0 on PyPI) - it is a bit tricky (impossible, without version checking all the libraries) to make code compatible with all the versions required. Thank you!

JimmyS83 commented 10 months ago

I second to that. Currently, pillow-simd cant be used with python 3.12 at all, as it seems

time4tea commented 9 months ago

I don't know how to make a PR against a branch that doesn't exist in this repo (simd/10.2.x) - but I have made 10.2.x version of pillow-simd at https://github.com/time4tea/pillow-simd/tree/simd/10.2.x , I think in the same way that you have made previous versions:

two checkouts: Pillow pillow-simd

add remote of pillow-simd in Pillow as simd git push simd 10.2.x:simd/10.2.x then rebase simd/master onto it.

There were a few conflicts which I hope i resolved. Hope that's useful? James

ogencoglu commented 5 months ago

Is this project maintained anymore?

schance995 commented 2 weeks ago

This package is still maintained, I see some commits from August/September. However, the project version is still not up to date yet.

@time4tea thanks for your work. Looks like the maintainers develop on the master branch and cut release tags from there. I don't think you need to create a new branch for your changes. Could you try to rebase the version 10.1 changes directly onto master and submit a PR?