Tomorrow (Wednesday, October 16) we plan to merge Python 3 support into Plone. Please do not merge anything until Sunday, October 21 to allow us some time to clean up and polish afterwards!
From now on all pull-requests for Plone 5.2 must work in Python 2.7, Python 3.6 and Python 3.7 and the pull-request-jobs in jenkins must be green for all three versions. We will make sure that the relevant jenkins-builds can be triggered for each pull-request and are triggered after each merge.
awesome! it would be very nice if someone can write documentation explaining to n00bies (like me) how to run Plone 5.2 in Python 2.7 and Python 3.7 so we can start testing our add-ons for compatibility ASAP.
I plan to add a Travis build just after the first alpha release.
Checkout buildout.coredev and then run ./bootstrap-py2.sh XOR ./bootstrap-py3.sh. Don't use both in one checkout. In order to share one builodut.coredev with two actual pythion versions, have a look at the simple wrapper I created at https://github.com/jensens/coredev52multipy (just run bootstrap.sh).
You don't need to. You can share eggs and src between both (python3 uses the __python__ folders for its byte-code files). I think the database is more the problem. Probably two different var folders should work. But I never tested it.