-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Include Pillow-SIMD in Pillow #2148
Comments
The reasons described here: https://github.com/uploadcare/pillow-simd#why-do-not-contribute-simd-to-the-original-pillow In short: we can't include this as is because it will break a lot of users. And there is no easy way to turn on this only for some users. |
@homm I understand that part. I'm just saying, you could probably move the project here but continue to do separate package releases, if you are interested in doing so. Otherwise, no worries. |
By "moving here" you are referring to the transfer "pillow-simd" repo to the "python-pillow" organization? |
Right, assuming you require a separate repo. Ideally you could just do SIMD stuff in a branch, or something. But yeah you are welcome to move the repo here if you like. |
Ok, thanks for the proposition. At the moment I want to have for Pillow-SIMD at least separate readme (which will not be so elegant in a branch) and issues (less important). There is a small announcement: I currently work on SIMD 3.4.0 release as well as Pillow-perf tools and page: http://homm.github.io/pillow-perf/ (just a beginning) Maybe when I'm done, we could move current SIMD readme to a documentation page. |
@homm Did this happen? I see https://github.com/python-pillow/pillow-perf … |
I'll close this issue. I see https://github.com/python-pillow/pillow-perf is now in this org. Just ping and re-open if you'd like to transfer https://github.com/uploadcare/pillow-simd over. 👍 |
@homm Just noticed https://pypi.python.org/pypi/Pillow-SIMD/3.3.2.post0 and wanted to explore the reasons why we don't include this in Pillow here.
The text was updated successfully, but these errors were encountered: