Am Montag, 3. September 2007 13:25 schrieb Martijn Faassen: > Hermann Himmelbauer wrote: > > Am Samstag, 1. September 2007 13:11 schrieb Andreas Jung: > >> --On 1. September 2007 16:33:58 +0530 Baiju M <[EMAIL PROTECTED]> wrote: > >>> Andreas Jung wrote: > >>>> --On 1. September 2007 16:00:19 +0530 Baiju M <[EMAIL PROTECTED]> > >>>> > >>>> wrote: > >Then it will be time to make Zope2/3 compatible > > with Python 2.6, which may not be that hard after all. After that it will > > be possible to slowly migrate from Python 2.6 -> Python 3, without > > breaking anything and without splitting Zope 2/3 in a Python 2 and Python > > 3 version. > > A slow migration is not really possible. You are to convert with 2to3. > There is the proposed scenario that you maintain the same codebase for > 2.6 for a while and release 3.0 versions by automatic conversion. Let's > just say I want to hear about practical examples of projects doing this > first. :)
Well, I personally don't have good experiences with automatic code conversion tools. Most often I had to manually edit the source. It may work in simple cases where e.g. "print" is replace with "stdout.write()" but if things get complicated, I'd rather not bet on such a conversion tool. I think it all depends on the amount/complexity of changes but we will see... Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
