Hi Jesus,
Am 13.02.2019 um 00:27 schrieb Jesus Cea :
> With less than a year away until Python 2.7 becomes "deadware", I wonder
> about the plan.
I am currently maintaining the Zope releases, so the plan currently looks like
the following:
* Zope 2.13 gets security fixes and maybe contributed
Hi Jesus,
maybe you are not aware of it, but Zope 4 runs both on Python 2.7 and
3.4+.
So, the recommended upgrade path would be something like this:
- update to the latest 2.13 version
- update to Zope 4 on Python 2
- update to Zope 4 on Python 3 (which makes ZODB conversion necessary)
I do
On 2/12/19 3:27 PM, Jesus Cea wrote:
With less than a year away until Python 2.7 becomes "deadware", I wonder
about the plan.
I am using Zope 2.13 under Python 2.7. Huge sites with ZODB sizes in the
multi gigabyte range. A handful of custom classes I could rewrite in
Python 3 if needed.
Is
With less than a year away until Python 2.7 becomes "deadware", I wonder
about the plan.
I am using Zope 2.13 under Python 2.7. Huge sites with ZODB sizes in the
multi gigabyte range. A handful of custom classes I could rewrite in
Python 3 if needed.
Is there any best practices I should be
