El 28/03/2008, a las 5:42, Sage La Torra escribió:
>
> I'll throw in my 2 cents too:
>
> I think machine based translation is iffy at best. I'm not the most
> up-to-date on py3k, but I have experience with other such projects (I
> wrote a Perl 5 to Perl 6 translator for Summer of Code 2006). This is
> just my opinion, but I think it would be best for Django (and most
> other python-based projects that are targeted at a large user bases)
> to wait until python 3 hits a version where it has stabilized and then
> do a port based on hand checking and modification of machine
> translated code.
>
> In general, the more versions of a language targeted by a project, the
> less efficient the project is. I'd say py3k is a great chance to
> 'start clean' more or less: deprecate the python 2.x code and have
> Django for python 3 be the official release.
>
> Python 3 makes it easy to get the right version to the right people.
> There will be one distribution for python 2.x and one for python 3.
> Django currently supports so many versions of python because so many
> are in use. Python 3 is a great opportunity to trim this down, make
> development easier, and still have something to give those who cannot
> or will not upgrade to python 3.
>
> This is, after all, just my opinion. If you choose to go forward with
> it, or if this gets accepted for Summer of Code, good luck with it, I
> look forward to seeing what you produce.
>
> Sage
>
+1
Think about what KDE did when porting the codebase to Qt4. There was
a translation tool released by TrollTech, but had exactly the same
problems Sage has mentioned: you're code wasn't optimized for the new
version of the toolkit. So, they decided to reimplemente a bunch of
things, breaking the API and the ABI, but taking full advantage of the
new toolkit.
On the other hand, it's usually a tedious task, but and the end of
the day, the benefits outweigh the hassle of rewriting some parts.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
