I was thinking about python2 clock

[Ty oc]

There have been new frameworks comming for 3.5> and I just found https://pythonclock.org/ so I wonder, if I can start migrating my web2py apps right now to the next version of web2py?

It is because I have a large rewrite and would love to use 3.5 or 3.6 for this.

[Leonel Câmara]

I'm guessing the rewrite will take some time. One thing you can do is to report any python3 problems you find with web2py while you do it. We'll fix them. 
 
We've fixed many many python 3 compatibility problems on the last months, you should be fine.

[Ty oc]

That means that I can run right now web2py on python 3.5 or 3.6? if I update to master? (my webpy version is a little old).

Nice! will try!

[Ty oc]

I think we2py should join the party!! and be on the list! :P

http://python3statement.org/

El martes, 20 de marzo de 2018, 16:14:58 (UTC-6), Leonel Câmara escribió:

[Richard Vézina]

Take care if you run your app under python 3... It a no way back because pickled object format change and you can't cleanly revert this change back... Try it with a copy of your app.

Richard

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Anthony]

On Thursday, March 22, 2018 at 3:26:31 PM UTC-4, Richard wrote:

Take care if you run your app under python 3... It a no way back because pickled object format change and you can't cleanly revert this change back... Try it with a copy of your app.

Of course it is a good idea to back up your app before making any changes, but I wouldn't say there is "no way back." Files that contain pickled objects are the *.table database migration files, session files, and error tickets. It is easy to generate a new set of *.table files by setting fake_migrate_all=True, and session files and error tickets are generally ephemeral anyway.

Anthony

[Ty oc]

I see, and in fact, yes, I was surprised to see that it run OK on first try on python3.

Thought this is a little pulling it off, it would be nice if I could run the pycharm check code for webpy modules and get 0 warnings or errors.


SO, I wonder, if you have a setup that "allow" this?