Basically web2py works with python 3. Not thanks to me but thanks to the 
many excellent contributors. Have you tried:

$ python3 web2py.py 

web2py with pyhton 2 and web2py with python use the same code base but are 
not compatible with each other for obvious reasons.

I am working on web3py which is not to be confused with web2py for python 
3. For this reason it will have another name. It will not be compatible 
with web2py (python 2 or python 3) but it will have a lot of the features 
that you like and more and be 10x faster.


On Wednesday, 5 April 2017 20:46:11 UTC-5, Dave S wrote:
>
>
>
> On Wednesday, April 5, 2017 at 1:15:55 PM UTC-7, JorgeH wrote:
>>
>> If what prevents the release of web2py python 3 ready are small details , 
>> why not release 2 versions, one for python 3, and the other one for python 
>> 3.
>>
>> Eventually, all the libraries will be ported to Py 3, or will be ways to 
>> sort that out.
>>
>> just saying
>>
>
>
> I think this is the plan being worked on.
>
> Massimo recently made a remark about having a post-2.14.6 release of 
> web2py, and the web3py stuff is accumulating. So far, they seem to have it 
> all in sources that can be used in either environment, so those changes 
> will be in the stuff you download in the 2.14.6-followon.  More changes as 
> the py3 stuff continues to work out.
>
> Because of things like pickling, you won't be able to switch back and 
> forth in place, but you shouldn't have to do a lot of changes to run in 
> either environment ... except that views/client-side stuff could change a 
> lot to be simpler, and perhaps SQLFORM won't be carried over (in favor of 
> js wrappers for FORM, AIUI).
>
> /dps
>
>
>> On Monday, April 3, 2017 at 3:59:52 PM UTC-5, Richard wrote:
>>>
>>> Good suggestion Paolo,
>>>
>>> I will try master asap, hope ealier than later as I am in the middle of 
>>> a big refactoring...
>>>
>>> I was just stand up for the other that may ask them self what's going on.
>>>
>>> :)
>>>
>>> Richard
>>>
>>> On Mon, Apr 3, 2017 at 3:01 PM, Paolo Valleri <paolo....@gmail.com> 
>>> wrote:
>>>
>>>> The best is to test your apps with python3 and report any issues. 
>>>> After a test period, I agree regarding pushing a new release
>>>>
>>>>  Paolo
>>>>
>>>> 2017-04-03 16:46 GMT+02:00 Richard Vézina <ml.richa...@gmail.com>:
>>>>
>>>>> Glad to hear that Leonel...
>>>>>
>>>>> But could we have "official" wrapup of the progress so far and where 
>>>>> we heading to. Are we waiting m2crypto to become py3 compatible to 
>>>>> release 
>>>>> a new web2py version?
>>>>>
>>>>> I am sure we could benefit from a new web2py version if the master is 
>>>>> not broken because of that (py3 compatibility) as we can still benefit 
>>>>> from 
>>>>> the improvement and bugs fixes that occur while keep using web2py with 
>>>>> python 2.7
>>>>>
>>>>> I am not saying that we should rush out a new release though as after 
>>>>> had waiting that long we surely can wait another 1-2 months and get py3 
>>>>> compliant version and 2.14.6 is reliable version.
>>>>>
>>>>> But, having a new version would help strengthen the code base, so 
>>>>> there will be less problem to figure out when py3 release will be ready, 
>>>>> don't you think? We will focus on py3 issue more easily then...
>>>>>
>>>>> Also, new version would help keep confidence that web2py is hear to 
>>>>> stay...
>>>>>
>>>>> Thanks
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 3, 2017 at 7:53 AM, Leonel Câmara <leonel...@gmail.com> 
>>>>> wrote:
>>>>>
>>>>>> Alex pretty much the only thing missing for py3 support is for 
>>>>>> m2crypto which web2py depends on for X509 stuff to support python 3, 
>>>>>> according to their repository 
>>>>>> <https://gitlab.com/m2crypto/m2crypto/merge_requests/65>they're 
>>>>>> really close to finishing py3 support. So I would say we're almost there.
>>>>>>
>>>>>> -- 
>>>>>> 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+un...@googlegroups.com.
>>>>>> 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 a topic in the 
>>>>> Google Groups "web2py-users" group.
>>>>> To unsubscribe from this topic, visit 
>>>>> https://groups.google.com/d/topic/web2py/UKcWKU66qnA/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> web2py+un...@googlegroups.com.
>>>>> 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 web2py+un...@googlegroups.com.
>>>> 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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to