{"id":3297,"date":"2019-05-06T09:28:37","date_gmt":"2019-05-06T07:28:37","guid":{"rendered":"http:\/\/blog.gocept.com\/?p=3297"},"modified":"2019-05-06T10:59:11","modified_gmt":"2019-05-06T08:59:11","slug":"zope-spring-cleaning-last-minute-information","status":"publish","type":"post","link":"https:\/\/blog.gocept.com\/2019\/05\/06\/zope-spring-cleaning-last-minute-information\/","title":{"rendered":"Zope Spring Cleaning: Last minute information"},"content":{"rendered":"

As the beta permission of Earl Zope<\/a> in Python 3 wonderland was extended in October 2018<\/a>, gocept invites Zope developers to the upcoming sprint from 08.05. till 10.05.2019 in Halle (Saale), Germany, to continue together on the work, which is still left.<\/p>\n

We aim to polish the last dusty spots on Earl Zope for the final permission to Python 3 wonderland aka the final 4.0 release. As Plone and other applications based on Zope have finally found a way to migrate a ZODB Data.fs<\/code> created with Python 2 to Python 3, the obstacles for this final permit are almost gone.<\/p>\n

So if you have questions concerning migrating databases, it is a good time to join or open an issue on GitHub. As many people are working on Zope during these days, the probability of a quick answer is high.<\/p>\n

As organizational tool to coordinate the work, we use GitHub projects again, as it allows cross-repository tracking of issues.<\/p>\n