Thanks for that info. I am about to start a new project which is also my 
first. So i would like to go with py4web. But i am nervous about not having 
good documentation for py4web.

Is the old documentation and videos etc that you have made (which are great 
- thanks) still mostly relevant?


On Monday, 16 December 2019 03:39:14 UTC+6:30, Massimo Di Pierro wrote:
>
> Good question.
>
> web2py and py4web share a lot of libraries and their syntax is very 
> similar. Both will be maintained.
> web2py was born in 2007 and it is mostly for Python 2 although it now 
> works well with python 3.
>
> As a rule of thumb, if you are porting a Python 2 project to Python 3, use 
> web2py.
> If you are starting from scratch, use py4web.
>
> py4web is ~20x faster. Code is much easier to read.
> They are both solid for production (except none works with py3.8 but we 
> are fixing that)
> They share pydal, templates, multi-app structure, ticket system.
> The request object and routing mechanism is different and py4web uses the 
> bottlepy ones.
> They both have an internationalization/pluralization system and the py4web 
> one is better but it lacks a UI (building one would be a good 1 day 
> project).
> They both have Auth but they are incompatible. The py4web is more modular 
> but less tested. (fixing those bugs is a priority, but need testers)
> web2py has SQLFORM, py4web has py4web.utils.form.Form. They are pretty 
> much equivalent but the latter does not support fields of type list:* (+)
> web2py has SQLFORM.grid and SQLFORM.smartgrid, py4web has Vue component 
> <mtable> They are pretty much equivalent but the latter does not support 
> fields of type list:* (+)
>
> (+) indicates things that are missing but we have no plan to add them. Th 
> world is moving to single page apps (vue, angular, react, etc.) and with 
> py4web we wanted to move away from generating complex HTML serverside 
> because it does not scale to complex projects. If you need tables and 
> complex interfaces, you should implement them in vue/angular/react/etc. So 
> we have no plans to add that functionality. What is considered good 
> practice has changed.
>
> Massimo
>
>
>
>
>
>
>
>
>
> On Thursday, 12 December 2019 06:17:05 UTC-8, icodk wrote:
>>
>> Should I use Web2py or py4web for a brand new project ?
>> What is still missing from py4web  ?
>> Can I debug with pycharm ?
>> I need all the great authentication I got with web2py : Registration,pass 
>> change, groups mail, etc.
>> smartgreed will be very nice to have or similar.
>> Stability ?
>> Can it be deployed with nginx  and pg ?
>> Thanks
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/web2py/0cc1fd87-a484-4bcc-9fed-745e449cae2b%40googlegroups.com.

Reply via email to