On Sunday, 2 June 2013 23:16:09 UTC-3, Anand wrote:

>
>
> On Friday, May 31, 2013, Tomas Schertel wrote:
>
>>
>>
>> On Monday, 27 May 2013 11:17:35 UTC-3, Tomas Schertel wrote:
>>>
>>> On Monday, 27 May 2013 11:08:20 UTC-3, Tomas Schertel wrote:
>>>>
>>>> On Thursday, 16 May 2013 10:02:21 UTC-3, Anand wrote:
>>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I've been wondering from long time about how to move forward about 
>>>>> web.py development. Here is the summary of my thoughts.
>>>>>
>>>>> Main Priorities:
>>>>>
>>>>> * Python3 support
>>>>>
>>>>> Python 3 is the future. We should make web.py ready for it.
>>>>>
>>>>> * Better integration with third-party tools
>>>>>
>>>>> web.py has not been very good at supporting integration with 
>>>>> third-party tools and making it easier for other people to write some 
>>>>> kind 
>>>>> of extensions to web.py. I think this is very important for the adoption 
>>>>> of 
>>>>> web.py.
>>>>>
>>>>> * Fixing the earlier design mistakes
>>>>>
>>>>> There are some design mistakes that I would like to fix.
>>>>>
>>>>> - The web.database module depends the request locals, which is a 
>>>>> design mistake. I've started a new project to make the database module of 
>>>>> web.py independent of other part of web.py. It is still work in progress. 
>>>>>
>>>>> https://github.com/anandology/**sqlpy<https://github.com/anandology/sqlpy>
>>>>>
>>>>> - We haven't got the form API is right. I've always extended form 
>>>>> class, overwritten some important methods, etc, whenever I've tried to 
>>>>> use 
>>>>> it. This needs to be improved.
>>>>>
>>>>> - Sessions. This another part of web.py that I'm not happy about. May 
>>>>> be this  should have been an extension instead of core part of web.py. 
>>>>> I'm 
>>>>> not really sure what to do about this.
>>>>>
>>>>> Please let me know your thoughts about this.
>>>>>
>>>>> If there are any parts of web.py that you think need to be improved, 
>>>>> or an API is not right, please let me know. 
>>>>>
>>>>> Anand
>>>>>
>>>>
>>>> Is pypy support planned?
>>>> uWSGI now works with pypy[1]. Maybe web.py could support it too.
>>>>
>>>> [1] - 
>>>> http://uwsgi-docs.readthedocs.**org/en/latest/PyPy.html<http://uwsgi-docs.readthedocs.org/en/latest/PyPy.html>
>>>>
>>>
>>> Armin Ronacher, from Jinja2, wrote about his experience on making Jinja2 
>>> support both python 2 and python3.
>>>
>>> [1] - 
>>> http://lucumr.pocoo.org/2013/**5/21/porting-to-python-3-**redux/<http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/>
>>>
>>
>> Hey Anand,  where are you? :)
>>
>
> Yes, I'm around. I've already seen that Armin's article. Lets see how our 
> porting goes.
>
> Anand
>
> -- 
> Anand
> http://anandology.com/


Hi Anand.
I'm just trying  to help you out, ok?
Have you seen these resources?

http://www.getpython3.com/#resources

Any news on migration?

See ya.

-- 
You received this message because you are subscribed to the Google Groups 
"web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to webpy+unsubscr...@googlegroups.com.
To post to this group, send email to webpy@googlegroups.com.
Visit this group at http://groups.google.com/group/webpy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to