So Python 2.x code is here published with Web3py name.
That is not criticism, I just describe the situation.
Maybe we would need other name for real Python 3.x version.
Something like Web23py (called "Twenty three framework") :)
I think the Python 3.x version would be really useful in this time or in
near future and most people can move to it.
As Python 3.x is not backward compatible, for Web23py is it not completely
necessary too.
What from my point could be good and important:
1.
more clear separated parts of the framework like PyDAL today is. Examples:
templating, markmin, wiki, plugin system, ....
2.
good separated (different?) templating characters {{ }} for the server side
and for modern javascript frameworks like vue.js where same is used
3.
if the idea "to use execscript and automatic imports" is not technically
+300% better but only +20% better, then leave it.
Because for lot of people this was "big" problem with Web2py, they left to
Flask or Django, and we have no much users/developers today - this is bad
for future.
So it would be better to use a standard technique for future and explicit
list of imports:
from gluon import a,b,c,d,..
and the people who want have easy and fast access to basic things, can just
import (regardless it is not recommended in Python doc's):
from gluon import *
Dne čtvrtek 14. ledna 2016 6:35:36 UTC+1 Massimo Di Pierro napsal(a):
>
> 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
> <javascript:>> 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.
