On Thu, May 16, 2013 at 9:02 AM, Anand Chitipothu <anandol...@gmail.com> wrote: > Python 3 is the future. We should make web.py ready for it.
+1, but my concern is this: https://en.wikipedia.org/wiki/Wsgi#WSGI_and_Python_3 Does that mean that the CherryPy web server will be replaced? > 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. I like A LOT that idea because I love the UNIX philosophy, you know: "write programs that do one thing and do it well. Write programs to work together". > 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. I want to work in the Form class! Give me this weekend to see if my idea is possible. I'll send an email explaining which design I think should be followed. > 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. +1. UNIX philosophy ;) And also, I found this email some time ago: https://groups.google.com/forum/?fromgroups=#!searchin/webpy/$20why$20sessions$20are$20bad$20/webpy/KHCDcwLpDfA/KOIC0vB27OoJ Having a session.py separated module seems the way to go (and also a separated openid.py module?). -- 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.
