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
Comments
@cgohlke Any issue with the current master becoming 2.1.0? |
I just opened issue #260. Otherwise, all builds and tests pass on Python 2.6 to 3.3, 32 and 64 bit, for Windows. |
I don't see _util mentioned anywhere, except in imports.
Also, I'm now seeing something along the lines of #260 when testing on a clean machine. |
Shouldn't "from PIL import Image.core as _imaging" be "from PIL.Image import core as _imaging"?
|
@manisandro Yep, thanks! |
Yes, I haven't done it yet. You are welcome to help 😄 |
I've got to figure out #264 first which I'm seeing everywhere, including Travis. |
Released! Thanks all |
brew remove libxcb libxdmcp
@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!
The text was updated successfully, but these errors were encountered: