Pillow: Release 5.0.0 Issue: 2018-01-01

[wiredfool]

Release issue placeholder for the ~4.4.0~ 5.0.0 Release.

[wiredfool]

if we're going to merge the PyTest PR, this is going to turn into a major (5.0) release, due to pytest's lack of support for EOL python 3.3. There are other potential breaking/major changes that might be worth merging.

• #2257, the pillow scripts rename/install issue.
• #2583, Decompression bomb warnings -> error
• #2339, Reworking the exception types that we throw.

[homm]

As part of the major release, I also would like to see #2198, because MRO could change call order.

[wiredfool]

I dislike #2198, especially WRT python2 required syntax, but also in terms of the MRO at runtime vs our build/test time.

[wiredfool]

I don't think I'm going to get to #2339 -- There's a lot of subsequently changed imports that are merge errors just to get to the point where it can merge, and then there are the reviews for if we're doing it correctly.

[cgohlke]

How about discontinuing bdist_egg and bdist_wininst binaries for Windows?

[wiredfool]

I'm OK with that, it'll need to be added to the release notes. Basically that means that they need pip of a reasonable recent version?

[wiredfool]

I've pushed the version bump, but have not tagged yet. I'm waiting on travis to get to the wheel builds, but it's being really slow about that.

[wiredfool]

Looks like we're getting a max of 2 concurrent builds right now, for comparison, appveyor finished before travis, which basically never happens.

[hugovk]

Travis is now green.

https://travis-ci.org/python-pillow/pillow-wheels/builds/323791158

[wiredfool]

Tagged 5.0.0

[cgohlke]

Windows binaries are ready.

[wiredfool]

Thanks @cgohlke

[wiredfool]

And we're uploaded and released

[radarhere]

Maybe this is just caching, but it looks to me like the 'Make sure the default version for Read the Docs is the latest release version' step in the RELEASING checklist hasn't been done?

[hugovk]

Thanks, I've put 5.0.0 as active and default, and 4.3.x and 3.4.x as inactive.

http://pillow.readthedocs.io/ ->
http://pillow.readthedocs.io/en/5.0.0/

[homm]

Close this?

[aclark4life]

@hugovk I'm switching back to "latest" on RTD to get rid of the Gratipay badge … probably fine to leave at current release otherwise.

[radarhere]

@aclark4life there has been mention of a potential 5.0.1, so if there was movement on that, you could include the removal of the Gratipay badge in that.

[aclark4life]

@radarhere Well, the issue is what do we configure RTD to do by default. I can see preferences for either… so if someone wants to switch from latest back to 5.0.1 after 5.0.1 is out, that's probably fine.

[wiredfool]

Just cherry pick the docs change onto the 5.x branch and push it. When we do a 5.0.1 release for the install issue, it'll roll up with the delivered docs.

[aclark4life]

Done (hopefully correctly)

[ThiefMaster]

Are there any backwards-incompatible changes? There is a long changelog, but in its current state it is kind of useless since it's mixing everything together in what appears to be chronological order. And as nice as e.g. using pytest is, when I'm just using a library I couldn't care less about something like this - what I do care about is whether I need to adapt some of my code or (manually) test every single place where Pillow is being used in my application.

[hugovk]

@ThiefMaster Yes, there are backwards-incompatible changes. Pillow 5.0.0 dropped Python 3.3, raises Exceptions for decompression bombs, and moved example scripts to their own package.

Check the release notes for details: https://pillow.readthedocs.io/en/latest/releasenotes/index.html