Ticket #13652 (closed PLIP: fixed)

Opened 3 years ago

Last modified 2 years ago

Drop Python 2.6 support for Plone 5

Reported by: timo Owned by:
Priority: minor Milestone: 5.0
Component: Unknown Version:
Keywords: Cc:

Description (last modified by davisagli) (diff)

Proposer: Timo Stollenwerk

Seconder: David Glick

Motivation

Supporting two Python versions for Plone 4.x has been necessary for a smooth transition to Python 2.7 and because most OS distributions used Python 2.6 as default Python interpreter.

Testing and supporting two Python versions requires quite some effort for core developers and package maintainers. This also makes our Jenkins setup more complex and requires more machines to run our tests.

Plone 5 gives us the opportunity for a clean cut off and it gives people enough time to prepare for an Python 2.7 upgrade.

Plone 5 is quite an ambitious project and we should focus on the important enhancements and not waste time on supporting old Python versions that aren't widely used any longer.

Assumptions

Python 2.6 is not the default Python interpreter on most OSes or support has been already dropped.

We will create Plone 4.3/5.0 branches for most if not all packages anyways, so we have a clear separation what versions support Python 2.6 and which doesn't.

Proposal & Implementation

Announce that Plone 5 will not officially support Python 2.6. Do not set up Jenkins jobs for Plone 5 - Python 2.6.

Deliverables

None

Risks

Site administrators running old OS versions and migrating from older Plone versions could complain or get upset.

Participants

Timo Stollenwerk

Change History

comment:1 Changed 3 years ago by timo

  • Version 4.4 deleted
  • Type changed from Bug to PLIP
  • Milestone changed from 4.x to 5.0

comment:2 Changed 3 years ago by timo

  • Description modified (diff)

comment:3 Changed 3 years ago by timo

  • Description modified (diff)

comment:4 Changed 3 years ago by davisagli

  • Description modified (diff)

I second this proposal.

Another reason is that support by the core Python team for security fixes for Python 2.6 ends in October 2013.

Supporting only Python 2.7 will let us clean up some things by taking advantage of things that were added to the language. For example we can use new unittest assertions and the nice data structures in the collections module.

comment:5 Changed 2 years ago by davisagli

  • Status changed from new to closed
  • Resolution set to fixed

This has been accepted for Plone 5.

Note: See TracTickets for help on using tickets.