Re: Zope Python 3.2 compatibility

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.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development

_______________________________________________
Zope-Dev maillist  -  [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iD8DBQFWqbUZkVdEXeem148RAmsaAJwIkG0bN00qRjdMUnQ3sv6hfMVvRQCfUmS1
T6rj8GF2FSb9tcsm4marppQ=
=i2Xe
-----END PGP SIGNATURE-----