Hi Green, Interesting points.
I had to drop the built-in DB library once I needed to connect to > multiple databases. I can see that Aaron raised a bug about this earlier: https://bugs.launchpad.net/webpy/+bug/131143 I also think it would be useful, and it shouldn't be too difficult to hack it. Also, have you had a look at Storm ( https://storm.canonical.com/ ) ? Storm is a proper ORM for Python, probably the nicest currently in existence. It was designed especially to make it easy to connect to multiple databases, and work with database schemas that are not derived from the class hierarchy. In a way, it can be as simple as web.py's database facilities (just don't use any of the relational stuff). I had to replace some of the request dispatching when I wanted to add > code that triggers on every request (eg. logging, transactions, custom > session management, "who's online?", traffic analytics). That's best done with WSGI middleware - cleanly supported by web.py. I had to drop the Cheetah integration to add internationalization > support - Cheetah supports the _ function, but only in precompiled > templates. I'm not sure I understand, is the problem doing the conversion dynamically, or extracting the translatable strings? Anyway, you don't have to use Cheetah (or Templator, the built-in templating language). In fact, I don't like either, and I always use something else. I find Genshi (both in txt and xml mode) to be great, but there are tons of alternatives. Neither are a dependency - just some extra bundled functionality. It's not a bad framework to start out with, but you will end up > needing to ditch nearly all of it by the time you've handled > everything a typical webapp needs. If I were to do it over again, I'd > probably start with Pylons. I'd consider Django, but I'm not sure you > can swap out Django components the way you can with Pylons. Sure, web.py doesn't amount to much - on a continuum stretching between, say a CGI script and Zope3, web.py is about one step above from WSGI - just enough to get you by. Web applications are, all-in-all, just programs that respond to HTTP requests. Whatever they do you may find that you need higher levels of abstraction to program them - web.py let's you do that whichever way you see fit, other, more elaborate frameworks force many of these abstractions on you, and I already hear that you are assessing them by how easily they allow you to 'swap them out'. Tom -- http://intellectronica.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
