Of course, option 2. It's the most logical path for all of us.

2016-01-14 23:43 GMT+01:00 Ovidio Marinho <ovidio...@gmail.com>:

> 2
>
>
>
> Sent with MailTrack
> <https://mailtrack.io/install?source=signature&lang=en&referral=ovidio...@gmail.com&idSignature=22>
>
>
>
>
>
>                    [image: http://itjp.net.br] <http://itjp.net.br>
>                      http://itjp.net.b <http://itjp.net.br>r
>           *Ovidio Marinho Falcao Neto*
>                  ovidio...@gmail.com
>                             Brasil
>
>
> 2016-01-14 20:14 GMT-02:00 Pbop <pbar...@maxit.com>:
>
>> Sounds like you have a good approach with option 2. That is my vote! You
>> can't get around that once a decision is made the community will react with
>> some degrees of enthusiasm and pushback.
>>
>> I am curious if the increase in performance is based on a more efficient
>> algorithm, Python3 is doing things faster or both?
>>
>> Keep up the good work.
>>
>>
>>
>> On Thursday, January 14, 2016 at 12:35:36 AM UTC-5, Massimo Di Pierro
>> wrote:
>>>
>>> It is another experiment.
>>>
>>> It is a rewrite of some of the web2py modules and supports 90% of the
>>> current web2py syntax at 2.5x the speed. It works. It it cleaner and should
>>> be easier to port to python 3 than current web2py.
>>>
>>> We are debating on web2py developers what to do:
>>> 1) backport some of the new modules to web2py (specifically the new Form
>>> class instead of SQLFORM)
>>> 2) try to reach a 99.9% compatibility and release it as new major
>>> version with guidelines for porting legacy apps
>>> 3) make some drastic changes in backward compatibility and release as a
>>> different framework (but change what? we like web2py as it is)
>>>
>>> For now I am working on 2 to see how far I can push the backward
>>> compatibility. But there are some functionalities I want remove or move in
>>> an optional module (from legacy_web2py import *).
>>>
>>> Feel free to share your opinion on web2py developers.
>>>
>>> Massimo
>>>
>>>
>>> On Wed, Jan 13, 2016 at 11:04 PM, kelson _ <kel...@shysecurity.com>
>>> wrote:
>>>
>>>> I was looking at your recent web3py commits and hoped you could provide
>>>> the web3py vision/intent (or point me towards it if I missed the
>>>> discussion).
>>>>
>>>> Thanks,
>>>> kelson
>>>>
>>>
>>> --
>> Resources:
>> - http://web2py.com
>> - http://web2py.com/book (Documentation)
>> - http://github.com/web2py/web2py (Source code)
>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "web2py-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to web2py+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> Resources:
> - http://web2py.com
> - http://web2py.com/book (Documentation)
> - http://github.com/web2py/web2py (Source code)
> - https://code.google.com/p/web2py/issues/list (Report Issues)
> ---
> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to web2py+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to