On Dec 10, 8:49 pm, Jacob Kaplan-Moss <[email protected]> wrote: > What do you think about using lib2to3 to write some custom > fixers to do some of this grunt work automatically? Might help people > port their Django sites/apps a bit easier, right?
On the face of it, I'd say it's doable, and perhaps worth it - it would be part of a generic toolset for single-code-base porting, and not especially Django-specific. But it won't make things automatic, there will probably always be *some* manual intervention required (unless a *lot* of time was spent putting intelligence into the fixers - that might be "how long is a piece of string?" territory). But yes, it would remove a fair bit of the grunt work. Of course, you need to be sure that a single code base strategy makes sense for you. Reading some of Chris McDonough's posts on reddit and elsewhere, it looks as if Pyramid is using the same approach. Perhaps the time is ripe to develop some special 2to2plus3 fixers ... Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
