Exactly, sofasurfer. I enjoy Python, and I wanted to start learning web development with it. However, I ran into the paradox of choices which represents Python web frameworks: lots of projects without any one standing out. I tried Django first only because I heard it was a Pythonic alternative to Rails, a beacon from the Ruby community. Still not satisfied, I was trying to look for the most minimal framework possible. I don't need an ORM. I don't need a magical template system. Start small and integrate in more complexity as needed! I think web.py is close to this view.
Architectural documentation would be useful. Perhaps I should write it as a way to learn the depths of the framework. Basically, what all the components given that compose minimal-foundation web.py applications and where can I later substitute more feature-rich subsystems from other projects? Such documentation would answer the question. On May 8, 6:24 pm, sofasurfer <[email protected]> wrote: > Nice effort! Anyhow, while I appreciate the web.py helper libs > cleanup, I do see the danger that your fork might become "Turbogears > Lite". > > You are right, there are 10+ specialized form processors that are > superior to web.py forms, 10+ template languages that are more > powerful than web.py templetor etc. But when you factor out all these > libs, the user will end in the turbogears dilemma: that he has to > learn not 1, but 4, 5 Frameworks to get his job done (plus the > syntactic sugar to connect them). > > IMHO the USP of web.py is that you can quickly build some site > prototype, run it, and then slowly replace the necessary components. > I'd have difficulties with this rapid prototyping if I needed to > understand 4 frameworks for the most basic tasks. > > Quoting Adam Atlas: > "Django lets you write web apps in Django. TurboGears lets you write > web apps in TurboGears. Web.py lets you write web apps in Python." > > -- Franz > > On 3 Mai, 19:56, Alice Zoë Bevan–McGregor <[email protected]> wrote: > > > Howdy! > > > On 2-May-09, at 12:45 PM, jlist9 wrote: > > > > What you did with web.py looks interesting. I like the template > > > processor :) I'm also glad to know about ToscaWidgets. > > > Thanks! ToscaWidgets is one of the components that was split off from > > the TurboGears project. > > > > I'm curious though, about the ORM you use, because it seems to me > > > that either of the well known ones (SQLObjects or SQLAlchemy) look > > > fairly heavy. Are you using one of those? > > > I'm using SQLAlchemy with the declarative layer. I'll be posting a > > complete packaged .egg example of a wiki and blog working off the > > examples from the web.py site using the dispatch and template parsers, > > and SA. Being able to connect to virtually any database and the clean > > declarative style are major bonuses to me. (Testing on SQLite, > > production on MySQL, for example.) > > > I'll be moving the db.py module into its own package to get added to > > the 'web.extras' namespace, that way the (quite elegant) DB helpers > > and custom templating language can be available if you need them, but > > not present if you don't. From import this: > > > Namespaces are one honking great idea -- let's do more of those! > > > — Alice. > > > smime.p7s > > 2KAnzeigenHerunterladen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
