This explains the situation well python3 vs python2 ,
http://blog.thezerobit.com/2014/05/25/python-3-is-killing-python.html
I think it made a big mess, not to carry the python2 internally in python3.
And python3 is a serious candidate to die. And this is not good.
[image: http://itjp.net.br] <http://itjp.net.br>
http://itjp.net.b <http://itjp.net.br>r
*Ovidio Marinho Falcao Neto*
[email protected]
Brasil
2015-11-19 11:39 GMT-02:00 Alessio Varalta <
[email protected]>:
> I think that for the programmer is not so important the version..always if
> the last is not too old..Python 2.7 is not too old but the problem that i
> see is that there is a good guide and good forum..web2py have many good
> features, but the real problem that I find( I am a web2py developer from 5
> months) is that there are low plugins and the low plugins have a bad
> documentation and low specific web2py library. For example php is old but
> there are many and many documentation, many library, many plugins and so
> many people but also many company use this language..Php is old but if you
> use this language you can find on google in 5minutes any information, you
> can create page in few time, many functionality in few time..So maybe is
> coul use the last version or the last framework example Play Java or
> another Python Framework or web3py but if you have a problem and there is
> any resources online and for one reserach and little problem spend hours is
> not the right way
>
> On Thursday, 19 November 2015 07:11:41 UTC+1, Carlos Cesar Caballero wrote:
>>
>> I think that backward compatibility, when we look it from the distance,
>> is more a bug that a feature.
>>
>> Let me explain before they fall on me like wolves...
>>
>> In my opinion, the backward compatibility restricts innovation, because
>> we do not know what will happen within the next five years, and the new way
>> to go can be difficult or impossible (I mean with impossible not feasible)
>> to adapt. The other thing is that with the time, there is lot of old code
>> making the framework bigger, slower, and harder to maintain.
>>
>> With this I dont say that we need to change things every week, is very
>> good always work thinking in backward compatibility, but can not be a
>> straitjacket.
>>
>> But that's just my opinion.
>>
>> Greetings.
>>
>> PD: I can take to write because I'll be out most of the time the next two
>> weeks.
>>
>> El 18/11/15 a las 20:22, Richard Vézina escribió:
>>
>> What about a relax about backward compatibility with web2py 3.0?
>>
>> On Wed, Nov 18, 2015 at 6:08 PM, Dave S <[email protected]> wrote:
>>
>>>
>>>
>>> On Wednesday, November 18, 2015 at 2:09:45 PM UTC-8, p a wrote:
>>>>
>>>> I like the idea of a new framework, using python 3 but that's not the
>>>> most important. These days if we want to attract developers to our projects
>>>> we also need to have an API, and separated front end and back end. web2py
>>>> is great for the backend. The DAL is fantastic, and every time I get close
>>>> to an ORM I appreciate it even more. After trying out ractive for myself, I
>>>> really like Massimo's idea of integrating web2py and ractive.
>>>> So I would love to see a new framework, if we can work on a clear
>>>> upgrade path that would take existing web2py apps to the new framework.
>>>> It's much easier to port a web app than a framework, on which many web apps
>>>> rely. I think we should release the web2py dev team from the chains of
>>>> backwards compatibility once every few years. If there is a new framework
>>>> based on the DAL and the other good stuff from web2py, but also using
>>>> ractive and other technologies and good ideas suggested on this list, then
>>>> porting our web apps would take a reasonable effort, and it would be well
>>>> worth it.
>>>>
>>>
>>>
>>> Maybe call it web2py-R ?
>>>
>>> /dps "only half in jest"
>>>
>>> --
>>> 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 [email protected].
>>> 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 [email protected].
>> 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 [email protected].
> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.
