On Sun, Apr 5, 2009 at 12:07 AM, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> This issue is not "porting". The issues are:
>
> 1) the database drivers have to be ported first. web2py and Django
> depend more or less on the same drivers
>
> 2) web2py supports the Google App Engine and that is Python 2.5. If we
> move to 3.0 your applications will not run anymore on the GAE. Google
> has no plan to move to 3.0.
>
> 3) A framework is not just based on Python. It requires that you code
> in Python. If people "port" Django to Python 3.0. Your Django
> applications will no longer work. The same is true for web2py.
>
> The bottom line is that we could port web2py to 3.0 in one week
> (technically it does not take much, except for str vs unicode we are
> already compliant) but it would be pointless to lose driver support,
> GAE support and break compatibility of all the current apps.
>
> When GAE moves to 3.0 and the database drivers for all supported
> backends become available we will release something like web3py (TM).
> Since we are going to break language backward compatibility that will
> also be a good time to include other non-backward compatible changes.
> 2010-2011 are reasonable dates but just a guess.
>
> You should not measure progress of a framework from this deadline, but
> from the number of commits.
>
> What feature of 3.0 do you consider so important to constraint you?

Specifically, none. I only would want to know about the future of
web2py to know when I'll have to "invest" in porting to Python 3.

-- 
 Álvaro Justen
 Peta5 - Telecomunicações e Software Livre
 21 3021-6001 / 9898-0141
 http://www.peta5.com.br/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to