-
Notifications
You must be signed in to change notification settings - Fork 86
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
pkg_resources.DistributionNotFound message after installing SIMD 4.3.0.post0 #17
Comments
@bjoernhaeuser did you solve it? I found that changed package name makes it fails. So now it's not drop-in replacement for Pillow anymore. In order to use it, it has to be required as Pillow-simd? |
Nope, did not solve it. But eventually stop trying it for running with thumbor. |
Ah. I did reference previous commit (which had old package name) and it seems to work. CC="cc -m$SIMD_LEVEL" pip install --no-cache-dir -U --force-reinstall \
git+git://github.com/uploadcare/pillow-simd@d87f2d67ea62d03432f76e33d428e0b07768c94a#egg=Pillow==4.3.0 |
@kkopachev also bumped into this. It's a bit weird that a drop-in replacement can't be used as a drop-in replacement because of a name change ;-) Or is there a way to use this in thumbor besides using an older version? |
Drop-in replacement refers to the same API and same functionality. Any installation issues are only installation issues and should not affect functionality once they solved. |
Could you give any pointers on how to solve the inatallation issue? I’m just using pip, but am getting the same error that was originally posted. The only workaround seems to be to pin the version to the one before the name change... |
Why ever thumbor checks dependencies on runtime? I suppose this is the root of the In one of my project where Pillow is requred by third-party library I also use egg parameter in requirements.txt |
I asked @kkopachev because he's a contributor to thumbor :) Admittedly, this issue is in a different repo. I'm not sure it's purely Thumbor's "fault" as such. I think they specify it under install_requires in setup.py, and to be fair, it used to work just fine when Pillow-SIMD was still named Pillow ... ... btw, If I'm reading this correctly, then #egg= is going to be deprecated |
@homm How do you use I created a local dummy package with following setup.py: from setuptools import setup
setup(
name='SomePackage',
version='0.0.1',
packages=['SomePackage'],
install_requires=[
"Pillow",
],
entry_points={
'console_scripts': [
'somepackage=SomePackage:main',
],
},
) and following in #!/usr/bin/python
import PIL
def main():
print (PIL.__version__)
if __name__ == '__main__':
main() Now, running Readme for pillow-simd requires to remove pillow first, and then install simd version.
That second command produces warning:
which results in freshly installed package to be named Pillow-SIMD:
making my
|
I guess there are 2 options from here.
Or make a custom entrypoint script. |
Now it's a bit clear to me. I haven't ever used I checked my config, there is
This prevents installation of Pillow and Pillow-SIMD simultaneously. Likely,
I believe this is the right way, but only with one correction: you can use
|
* updated based on reiew comments from @kkopachev - adding a comment on pinning to pip 9.0.3 - updating Pillow-SIMD to latest supported version 4.3.0.post0 - updating docker-entrypoint to use `python -m thumbor/server` to avoid thumbor not finding Pillow see uploadcare/pillow-simd#17 * removed unused thumbor-multiprocess-simd
Also running into this issue with deluge now (https://dev.deluge-torrent.org/ticket/3282). It seems that pillow-simd just isn't a drop-in replacement for when Should this become a feature request in setuptools or can it be solved on pillow-simd's side? |
What did you do?
Execute these commands (Dockerfile) from a CentOS 7 base image:
What did you expect to happen?
That pillow-simd is a replacement package for pillow.
What actually happened?
I get this this error message when running thumbor:
What versions of Pillow and Python are you using?
Pillow: 4.3.0.post0
Python: 2.7.5
The text was updated successfully, but these errors were encountered: