On Tue, Mar 4, 2008 at 9:55 AM, Jose Galvez <[EMAIL PROTECTED]> wrote: > this is an interesting issue, because I would suspect that all our pylons > applications will have to be converted as well as the pylons base code.
At my workplace it's mostly web apps, wxPython apps, scientific calculation, TRAC, and we're considering Plone. So I think we'll wait until Pylons and wxPython have made the switch, and then convert our stuff. Pylons has acknowledged the issue but has not set any schedule for conversion. Both Pylons 1.0 and Python 3.0 are supposed to be released in late summer. Python 1.0 will drop the backward-compatibility cruft that accumulated as it evolved, so post-1.0 will be the best time to do the conversion. > I > know that there is going to be a program which will automate the > translation, but not having used it I don't know what issues the translation > will cause. Supposedly it will do the tedious work but you'll still have to review the code afterward for untypical or unusually dynamic cases that it may not catch. There will be a checklist of things to look for. Also, if you have a comprehensive test suite, you can just run it and see if it passes. > The other big question is will eggs will they be able to tell > the difference between python 2.x and 3.x since the code will be different I haven't heard anything about this. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
