This is of course also true for Plone 5.2.įor a client of me, core changes in the Plone 5.2.9 release caused a problem in an ecosystem package (Mosaic). Summary: A change should make Plone more stable, not less stable. I July I created a post about rules for Plone 6 development during the beta stage. We will see this for Plone 6.0 as well: if the Python community drops support for a Python version, Plone will stop testing with it. You should plan on using Python 3.8 then. Sure: if it proves easy enough in practice, then we could decide to continue testing, but you should not count on it. At that point, Plone 5.2 will stop testing with it. If you followed the link to the Status of Python versions, you will see that Python 3.7 reaches end of life on June 27 2023, so in about 9 months. It is highly recommended to take this third step! Please do not linger in step 2. Migrate Plone 5.2 to Python 3.7 or 3.8.

This is needed as a stepping stone if you do inline migration: Note that Plone 5.2 still supports Python 2.7, even though this is end of life since January 2020. If you find such a problem, please report how you fixed it, so we can include a proper version pin for 3.6 in the next release. Switching back to an older version should help here. You may get a new version that breaks on Python 3.6. The biggest problems that I expect to come up, are in third party packages.If a fix is available, I will happily include it in the next 5.2 release. If you find a problem that is specific to Python 3.6, please still report it.We just cannot guarantee that it still works, because we cannot run the tests. We will not actively try to break Python 3.6.It has already not worked for the past few weeks. We will stop testing Plone 5.2 with Python 3.6, effective immediately.So: Plone 5.2 drops support for Python 3.6 We feel it is not a good use of the time of our volunteers to try to keep supporting it. It has reached end of life already in December last year, as you can see in the Status of Python versions. Python 3.6 itself is no longer supported by the wider Python community. After some recent upgrades to our Jenkins testing server it is proving difficult to get Python 3.6 running on that server.