Plone 5.2.12 released

Announcements
1

Release notes for Plone 5.2.12

If you want to jump straight in, here are two important links:

Highlights

Major changes since 5.2.11:

  • plone.recipe.zope2instance: Add new option asyncore_use_poll to waitress config file.
  • plone.app.locales: Update Turkish translations.
  • plone.app.users: For user schemas use a volatile cache on the request instead of on the portal. This prevents seeing an empty user profile when you have custom user schemas.
  • plonetheme.barceloneta: Fix Diazo rule problem with undefined footer_portlets and footer_portlets_count variables.
  • Products.CMFPlone:
    • Show warning in Site Setup when using an unsupported Plone or Python version.
    • Removed path query from search view when context is site root.
    • Fixed encoding issue on Python 3 for some mail servers. This could result in missing characters in an email body.

Python compatibility

This release supports Python 2.7, 3.7, and 3.8.

Important: This is the last release that officially supports Python 3.7.

The next Plone 5.2 release is expected in July, but Python 3.7 will reach end-of-life in June.

We will stop testing on 3.7 and stop providing specific version pins for 3.7 (none are needed at the moment though). This means that things may start breaking without being noticed. If something breaks and you can supply a fix, we are happy to include it in the next release though.

Python 3.6 support was dropped in Plone 5.2.10.

Plone 5.2 supports Python 2.7, but this is end-of-life since 2020. It should only be used as a temporary stepping stone before you migrate your Plone site to Python 3.

Versions of pip, zc.buildout, setuptools

In Plone core we use these versions to install Plone on Python 2:

setuptools==42.0.2
zc.buildout==2.13.8
wheel==0.37.1

and these on Python 3:

setuptools==65.7.0
zc.buildout==3.0.1
wheel==0.38.4

In general you are free to use whatever versions work for you, especially newer ones, but these worked for us.

Note that setuptools 66 is more strict with what versions it can recognize. If you run pip or buildout and it suddenly cannot find a package with a non-standard version, then this may be the cause. This is why we stayed at version 65 for this release. Likely, we will keep doing this for future Plone 5.2 releases.

Installation

For installation instructions, see the documentation.

Issues

If you find any issues, please report them in the main issue tracker.

1 Like