Hi Anand, I used weby+sqlalchemy in my project (www.tatilsefasi.com) which is about outgoing tour packages. Users send request about tours and sales consultants sell it by manuel. There is no online payment option because providers doesn't support online sale for outgoing tour packages. Next step is online hotel booking. I ll integrate(xml) with some providers.
2013/10/28 Ole Trenner <[email protected]> > Hi Anand, > > [tl;dr at the bottom] > > first of all I'd like to thank you and all contributors for the efforts > they're putting into web.py. It's one of my most favorite (if not THE most > favorite) web frameworks/libraries, even across other programming languages. > > I've been using it for small, uhm, web projects (go figure!), both > frontend and api/service stuff. I've written a small content management > system which is based on web.py. I guess web.py is somewhere to be found in > every web related python project I've done in the last years. > > The thing I love most about web.py is that as I'm starting a project it > provides a basic skeleton or scaffolding. It contains all the tools and > things needed to get the project started right away. Just import web and > off you go. > And then, as the project is evolving and developing more specialized > requirements, I can take out specific bits and pieces and replace them with > more specialized solutions or dedicated libraries. > This 'evolving' approach feels very natural to me and web.py supports it > much better than most 'all-in-one' solutions. > > Another thing I love about web.py is that it is not dogmatic about the > project structure. Sure, over the years I have converged towards a specific > structure, but that structure is mostly influenced and shaped by deployment > requirements and the hosting environment, not by some directory structure > that is required by the framework. That kind of freedom is very nice and > liberating. > > When thinking about some sort of wishlist, I should probably go with the > parts of web.py I end up replacing over time. The first thing to go would > be the templating engine, followed by the form handling. To me, they feel > somewhat clunky and unintuitive, so sometimes I don't even bother using > them at all. The next thing would be the database layer, although it is > surprisingly versatile. > > Then there are some things that are completely missing, like asynchronous > stuff or threading support, but they are very application specific and not > needed every time. > > Then there are some minor issues with the web.py api, for example the > routing/url definition. This loooong flat list is just so unforgiving, > especially if you want to adjust it programmatically. It'd be great if we > had some more options for that (maybe a dict? nested lists? resolver > classes?). > > I guess it'd be a big improvement if the application class was structured > a bit differently so that extending it by subclassing was easier (or at all > possible, I'm looking at you, handle_class()). > > On the other hand it is a good thing that the api of web.py has been so > stable over the years. > > It is also quite enjoyable to read the web.py source code. To me it has > been an available and complete replacement of documentation. I'd even say, > don't try and make a better documentation, just make it easier to read the > source code. > > tl;dr: web.py is great, please don't change the foundation, although it > probably could use a slightly more flexible api and an improved, > extension-friendly code structure. > > Cheers, > Ole. > > > Am 27.10.2013 um 23:12 schrieb Anand Chitipothu: > > > 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. > > > > 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 > > * a way to write web.py extensions so that it is easier to use > third-party libraries along with web.py > > > > What about you? > > > > 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. > > -- > Ole Trenner > <[email protected]> > > > > > -- > 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. > -- Aydın Şen -- 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.
