Andrew Murray
Andrew Murray
Hi. This looks like a duplicate of https://github.com/python-pillow/Pillow/issues/1146
#6557 has been merged instead, resolving the inconsistency by replacing `PIL.Image.Resampling.NEAREST` with `Resampling.NEAREST`.
I've created PR #6445 to resolve this.
Remind me why 3.3 isn't activated in AppVeyor? If it was initially disabled for speed, that would have made perfect sense at the time, but the builds are much faster...
It passes - https://ci.appveyor.com/project/radarhere/pillow/build/3.0.pre.173 - and so I've created a PR.
At the end of [an AppVeyor build](https://ci.appveyor.com/project/python-pillow/pillow/build/job/q5w7sd5cvgqjwm1w), it outputs > Uploading artifact Pillow-6.1.0.dev0-cp37-cp37m-win32.whl (1,064,340 bytes)...100% > Uploading artifact Pillow-6.1.0.dev0-py3.7-win32.egg (1,469,913 bytes)...100% > Deploying using S3 provider > Uploading artifact "Pillow-6.1.0.dev0-py3.7-win32.egg"...
@nulano given that #4495 has [significantly improved](https://github.com/python-pillow/Pillow/pull/4495#pullrequestreview-395900016) compiling Pillow on Windows, do you think there's anything left to do here?
Could you put together a simple script demonstrating the problem?
What do you think of working from the end instead, subtracting the width of 'adise' from the width of 'paradise'? ```python from PIL import ImageDraw, Image, ImageFont img = Image.new('RGBA',...
I'm not able to replicate this on my macOS machine. Does this happen for you on Ubuntu? While unlikely, I don't suppose that the problem is just that some of...