We use web.py to provide five features in our application suite - three user interfaces and two REST APIs. Combined, these applications are over 50k lines of code. Our open source component is http://cato.cloudsidekick.com
(I also used it for a smallish Flexible API project that I can't seem to find the time to keep active. https://github.com/shannoncruey/FlexAPI) Original versions of our tools were written on Windows in ASP.NET (C#). When adding support for unix platforms, we originally tried Mono, but decided quickly a refactor to Python was the best approach. We selected web.py because it was incredibly lightweight and easy to use, especially since we were fairly new to Python at the time. Other frameworks have high learning curves, and assume you'll build applications from scratch in their metaphor, which we had neither the time nor desire to do. With the help of web.py and a C# to Python conversion tool we wrote, we moved the entire application from C# to Python in less than two months. Converted from C#, we had already solved several problems so we did not use web.py database access at all. We use the templator, but it's only purpose was to support the "Master Page" concept from ASP. (The applications are 100% client side script + Ajax, so templating wasn't needed.) We use Sessions (using shelf - files caused pickle errors for some reason). Our application talks to MongoDB, SQL Server, Oracle and MySql. We have hundreds of "endpoints" in our API, but my 'urls' list only has a few entries - I use code to look at the path and decide which internal function to call. I love web.py because the core is solid and doesn't force me into any particular design. Aside from eventual Python 3 support, I hope there are no material changes to the core. In fact, for my part the database and templating could be removed and turned in to add-ons. Connecting to a database, or building a form directly in HTML is such standard fare these days, in my opinion it's best to just build forms natively and manipulate them client side. (Of course, as I said above I'm tilted in that regard, as I think client side script + Ajax has served us *very well*. Documentation is my only complaint. What paltry bit is out there is confusing, and some of it still applies to older versions. If the documentation was moved to a wiki, I'm sure this entire group would contribute. We've solved problems with Session, global exception handling, setting Content-Type, requiring auth on only certain pages, web.input versus web.data, the list goes on, all without documentation. Make a wiki. If you build it, they will come. :-) Awesome tool! NSC On Mon, Oct 28, 2013 at 6:47 AM, Steven Brown <[email protected]> wrote: > On 10/27/2013 06:12 PM, Anand Chitipothu wrote: > > Hi, > > I would like to know who is using web.py, what they like about it and > what features they wish to have. If you are using web.py for any of your > projects, please let me know. > > I am using web.py to make a webapp to track stuff that members in a club I > belong to do to benefit the club. Once you take into account members, > their chapters, and the people that verify things, and many other things, > it's more complicated than you might think! > > > Let me start with myself. > > I use web.py for openlibrary.org. Its been running from quite some time > and I usually don't add ton of new features except some minor changes once > in a while. > > My wishlist: > > It is quite some time since I've built any new applications using > web.py, but wish web.py had the following: > > * nice documentation. it would be nice to have sphinx documentation for > web.py > > Oh please, dear God in Heaven yes. Admittedly I may be spoiled by the > general python and C/C++ documentation, but web.py documentation is sorely > lacking. It is plenty adequate to getting someone started; that's actually > something I really like. But when you need to look up a syntax, it > just....well, sucks, if I'm being honest. Maybe I'm approaching it wrong, > and I'm still learning, but usually when I am having trouble matching up > different parts of my code, I am sticking in lots of "print type(...)" > statements to see what exactly I'm working with. I would much rather be > able to just look that stuff up. And in general, just more fleshed-out > documentation would be an amazing help; not to mention it would make it > easier for me to sell others on it! > > * a way to write web.py extensions so that it is easier to use > third-party libraries along with web.py > > What about you? > > Ole mentioned a better forms library, and I heartily agree. Templator has > been pretty straightforward for me, but I'm not doing anything especially > complicated with it. One small feature I would love to have, so much so > that I implemented it myself, is a bit more flexibility on options in > select elements. I use a JS library that updates a select's options when > you select from another one (so that you can eg select make of car, and the > next select gets populated with all models of that make). > > Those are the big things, but other than that, I absolutely love the > simplicity and low overhead in this framework! It's my first that I have > really dived in to use, after being terrified by the seeming-to-a-beginner > opacity of Django. Great work overall, let's make Aaron proud! > > > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/webpy. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/webpy. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy. For more options, visit https://groups.google.com/groups/opt_out.
