Just tested, some considerations:
1. Tested with Python 3.6, followig strictly the provided instructions,
several things don't work:
a) static folder is not working properly. I get a 404 error for all the
requests
127.0.0.1 - - [28/Mar/2019 10:45:10] "GET /todo/index HTTP/1.1" 200 828
127.0.0.1 - - [28/Mar/2019 10:45:10] "GET /todo/static/js/sugar.min.js
HTTP/1.1" 404 774
127.0.0.1 - - [28/Mar/2019 10:45:10] "GET /todo/static/js/axios.min.js
HTTP/1.1" 404 774
127.0.0.1 - - [28/Mar/2019 10:45:10] "GET /todo/static/js/vue.min.js
HTTP/1.1" 404 770
127.0.0.1 - - [28/Mar/2019 10:45:10] "GET /todo/static/js/todo.js HTTP/1.1"
404 764
b) favicon requests also produce a python error:
27.0.0.1 - - [28/Mar/2019 10:44:47] "GET /favicon.ico HTTP/1.1" 404 742
Traceback (most recent call last):
File "/opt/src/web3py/web3py.py", line 149, in load
self.data = jwt.decode(enc_data, self.secret,
algorithms=[self.algorithm])
File "/opt/src/web3py/venv/lib/python3.6/site-packages/jwt/api_jwt.py",
line 84, in decode
payload, _, _, _ = self._load(jwt)
File "/opt/src/web3py/venv/lib/python3.6/site-packages/jwt/api_jws.py",
line 177, in _load
binary_type))
jwt.exceptions.DecodeError: Invalid token type. Token must be a <class
'bytes'>
2. About your questions:
- sqlform and grid are one of the key points for web2py. It's one of the
main reasons to use it instead of other frameworks as development is really
quick. However I think nowadays a backport from web2py is not a good idea.
We should provide something optional based only on vue.js. As you say, we
can do it better.
- auth is not as important in my experience. It has never been the
reason to pick web2py and there are other ways to do it.
3. about the new ideas:
- I love the use of jwt and vue.js
- I love it does not use custom import or eval. That will make testing
much, much easier and logical.
- I would like to have a kind of automatic integration between the
backend and webpack, for modern development. It should be optional
obviously, but something like django-webpack-loader should be added (or
have web3py-webpack-loader as an external library that can be installed if
required)
If you have a roadmap where others could lend a hand, please, tell it.
Maybe creating some github issues that could be assigned to volunteers. I'd
be glad to help.
José L.
El jue., 28 mar. 2019 a las 10:16, Massimo Di Pierro (<
[email protected]>) escribió:
> I know this comes up once in a while but ...
>
> https://github.com/web2py/web3py
>
> what do you think?
>
> It is very preliminary but I will have an admin soon.
> Backporting SQLFORM, grid and Auth, should not be that complicated,
> although I think we can do better.
>
> Massimo
>
> --
> 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.
