Zope 4 is already in beta, time to move applications running on Zope to Zope 4.
Zope 4 supports Python 3, time to move application running on Zope to Python 3.
The Zope-4-Welcome-Sprint is a chance to move forward with Plone and other applications built on Zope.
gocept hosts this sprint in Halle (Saale), Germany from May, 16th to 18th.
You are heartily invited to welcome Zope 4 in the Python 3 wonderland and help his friends to also start to live there.
I think Jan confirmed last week that he's coming to Halle for the Zope-4-Welcome-Sprint. If there's anything he should prepare in advance just let me know
That's nice. To effectively contribute to Zope resp. Plone a signed contributor agreement for each of the organisations is required. If he already have them, no worry about further preparation.
Create two coredev-buildouts for Plone 5.2 on your laptop. One for Python 2 and one for Python 3.
Why? Because the py3-config uses a lot of custom branches and you would waste a lot of time switching python-versions and running buildout when you do not separate these to simply try some feature in python2. They can share the same buildout-cache.
At the beginning of the sprint we will split into teams that work on different tasks. There are a lot of things that need to be done and here are some issues that we'd love to work on during the sprint:
Finish porting plone.testing (i.e. modify test-layers to use wsgi instead of ZServer) and start porting plone.app.testing. Currently we cannot even run a single test because we have no test-layer in py3 that provides a plone-instance
Start a instance and fix a feature that does not work yet in py3. There are plenty of these and it is fun to hunt and fix these issues. I will bring a list of broken features to the sprint
As a small motivation-token here is a screenshot of the Plonesite I just created in Python 3. Today I finally found the time to fix a issue that broke creating a new site.
@Rotonen actually I have no plan
Whenever I have some time I try to pick a package and make the test run for both Pythons and the current tox configuration (even if it is not perfect) is something that makes this quite convenient.
One to solve before the sprint if possible, is this one:
This is the problem causing our jenkins builds to hang some times.
See:
and
It can also be reproduced outside of running tests. Sometimes when stopping Zope, it will end with a keyerror instead of closing down nicely. This can probably cause issues with proper reporting of shutdown (docker etc.)