Skip to content
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

Issue warning(s) re: import _imaging breakage coming in 2.1.0 #249

Closed
aclark4life opened this issue Jun 14, 2013 · 8 comments
Closed

Issue warning(s) re: import _imaging breakage coming in 2.1.0 #249

aclark4life opened this issue Jun 14, 2013 · 8 comments
Milestone

Comments

@aclark4life
Copy link
Member

@olt FYI we are releasing 2.1.0 in 2 weeks, at which point "import _imaging" will fail (instead please use "from PIL.Image import core as _imaging")

If you are interested, please help us get the word out about this change!

@aclark4life
Copy link
Member Author

@cgohlke Any issue with the current master becoming 2.1.0?

@cgohlke
Copy link
Contributor

cgohlke commented Jun 30, 2013

I just opened issue #260. Otherwise, all builds and tests pass on Python 2.6 to 3.3, 32 and 64 bit, for Windows.
PyPy 2.0.1 it crashes during test_imagefont.

@wiredfool
Copy link
Member

erics@builder-1204-x64:~/Pillow$ python selftest.py
Traceback (most recent call last):
  File "selftest.py", line 17, in <module>
    from PIL import Image
  File "/usr/local/lib/python2.7/dist-packages/Pillow-2.1.0-py2.7-linux-x86_64.egg/PIL/Image.py", line 84, in <module>
    from PIL._util import isPath, isStringType
ImportError: No module named _util

I don't see _util mentioned anywhere, except in imports.

erics@builder-1204-x64:~/Pillow-master$ grep -r _util *
build/lib.linux-x86_64-2.7/PIL/OleFileIO.py:from PIL._util import isPath
build/lib.linux-x86_64-2.7/PIL/JpegImagePlugin.py:from PIL._util import isStringType
build/lib.linux-x86_64-2.7/PIL/ImageQt.py:from PIL._util import isPath
build/lib.linux-x86_64-2.7/PIL/ImageFile.py:from PIL._util import isPath
build/lib.linux-x86_64-2.7/PIL/ImageCms.py:from PIL._util import isStringType
build/lib.linux-x86_64-2.7/PIL/Image.py:from PIL._util import isPath, isStringType
build/lib.linux-x86_64-2.7/PIL/ImageFont.py:from PIL._util import isDirectory, isPath
build/lib.linux-x86_64-2.7/PIL/GdImageFile.py:from PIL._util import isPath
build/lib.linux-x86_64-2.7/PIL/ImageOps.py:from PIL._util import isStringType
build/lib.linux-x86_64-2.7/PIL/ImageDraw.py:from PIL._util import isStringType
PIL/OleFileIO.py:from PIL._util import isPath
PIL/JpegImagePlugin.py:from PIL._util import isStringType
PIL/ImageQt.py:from PIL._util import isPath
PIL/ImageFile.py:from PIL._util import isPath
PIL/ImageCms.py:from PIL._util import isStringType
PIL/Image.py:from PIL._util import isPath, isStringType
PIL/ImageFont.py:from PIL._util import isDirectory, isPath
PIL/GdImageFile.py:from PIL._util import isPath
PIL/ImageOps.py:from PIL._util import isStringType
PIL/ImageDraw.py:from PIL._util import isStringType

Also, I'm now seeing something along the lines of #260 when testing on a clean machine.

@manisandro
Copy link
Member

Shouldn't "from PIL import Image.core as _imaging" be "from PIL.Image import core as _imaging"?

>>> from PIL import Image.core as _imaging
  File "<stdin>", line 1
    from PIL import Image.core as _imaging
                         ^
SyntaxError: invalid syntax

@aclark4life
Copy link
Member Author

@manisandro Yep, thanks!

@aclark4life
Copy link
Member Author

Yes, I haven't done it yet. You are welcome to help 😄

@aclark4life
Copy link
Member Author

I've got to figure out #264 first which I'm seeing everywhere, including Travis.

@aclark4life
Copy link
Member Author

Released! Thanks all

radarhere pushed a commit to radarhere/Pillow that referenced this issue Sep 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants