First of all, thank you all for your hard work: web.py is just amazing! On Thursday, May 16, 2013 3:02:21 PM UTC+2, 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. > Rather than adding support for integrating with third-party tools, what this framework really lacks of is a central archive containing guides, tutorials, best practices of how to use web.py in production-like environments. I mean, I had no issues in using web.py with celery, sqlalchemy, webassets or wtforms, even if the framework lacks of extensions support. The site already offers a wiki and a cookbook with useful recipes but we definitely need to keep them up to date with new technologies etc. > > * 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 > What is the purpose of the database module? I think the reason it has been included in the framework is simply to enable users to create applications without linking external libraries or tools (one cannot think of a web-app without a database interface). But, does the database module really want to take the place of other ORMs (e.g. SQLAlchemy)? With that said, I see the design problem and I think it should be fixed. > > - 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. > Let me think about that. I will get back to the list as soon as I have collected some ideas. Cheers, Matteo > Anand > -- 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.
