Op 28/01/16 om 07:28 schreef Marius Gedminas:
On Wed, Jan 27, 2016 at 12:40:52PM -0500, Tres Seaver wrote:
On 01/27/2016 08:51 AM, Marius Gedminas wrote:
On Wed, Jan 27, 2016 at 02:17:17PM +0100, Maurits van Rees wrote:
As Marius asked on the pull request (https://github.com/zopefoundation/zope.publisher/pull/10) I am raising the question: do we want to keep supporting Python 3.2 in Zope? Quoting him: "The Zope project as a whole needs to make a decision about continuing to support Python 3.2 now that large parts of the ecosystem no longer support it."
I would say we can drop it. That would mean removing py32 from the Travis/tox files.
I'm +1 for dropping Python 3.2 support for all zopefoundation packages.
If there's consensus, I can probably do that easily with a shell oneliner -- I've all of them conveniently checked out.
I'd be fine with dropping 3.2 and 2.6 support entirely on them all. Required changes would include:
- Dropping 2.6 and 3.2 from tox and travis. - Dropping them from the Trove classifiers. - Bumping the minor release number. - Adding a changelog entry (with the new, targeted release number).
Bumping version numbers and adding changelog entries are a bit beyond my shell-fu, and I retract my offer for a mass change.
Removing the Trove classifiers can be done with this shell script: #!/bin/sh # Remove Python 2.6 and 3.2 classifiers (and lower) from setup.py. cat setup.py | grep -v 'Programming Language :: Python :: 2.3' | grep -v 'Programming Language :: Python :: 2.4' | grep -v 'Programming Language :: Python :: 2.5' | grep -v 'Programming Language :: Python :: 2.6' | grep -v 'Programming Language :: Python :: 3.0' | grep -v 'Programming Language :: Python :: 3.1' | grep -v 'Programming Language :: Python :: 3.2' > setup.py.tmp mv setup.py.tmp setup.py git diff setup.py echo "Commit this? [ENTER means yes, anything else means revert] " read answer if test "x$answer" == 'x'; then echo "committing" git commit setup.py -m "Removed Python 2.6 and 3.2 classifiers (and lower)." else echo "Reverting setup.py." git checkout -- setup.py fi I am looking if I can create a new command in zest.releaser to add a changelog entry that you pass on the command line. Bumping versions: can be easily done with zest.releaser when doing a release. But if you are not yet creating a release and only want to update the development version, this cannot be done yet. I might be able to add that too. Normally not too useful, but in batch it can be handy. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl