ºÝºÝߣ

Editor's Notes

• #2: Disclaimer: I haven't built any sort of large-scale, high-traffic Pylons app, nor gotten rich from it. Hire me and let's build one :-) Thanks for George's coverage of HTTP protocol in his mod_python talk in December
• #3: Rails, Django; use existing libraries, please! Reasons of philosophy don't want to bash Django -- all in all I think it's a nice framework and good for Python. I make comparisons because I assume that many are familiar with it Ruby can be a little Perl-like, which should scare you. Also so many DSLs and metaprogramming makes me worry about the Law of Leaky Abstractions...
• #5: WSGI to the core, setuptools
• #6: The developers of the central pieces are working closely together, and mostly try not to break APIs in major ways Not much in the way of off-the-shelf apps yet. It's not Plone, there are not built-in widgets or a spiffy auto-admin like Django You will spend some time getting familiar with the components and what does what. Fewer decisions are made for you -- flexibility comes at the cost of doing some homework and having ideas about what you want before diving in. As always, use the right tool for the job.
• #7: Ben Bangert - Lead Dev, O’Reilly Pylons, Routes, Beaker, WebHelpers Mike Bayer - Myghty, Beaker, Mako, SQLAlchemy Ian Bicking - Paste, FormEncode, virtual/workingenv
• #10: Flexible deployment options, ability to jump ship to a different server architecture Paste is essentially a WSGI toolkit. Provides conveniences for lower-level WSGI apps or rolling your own framework. Pylons builds on Paste in much the same way that TurboGears 1.0 built on CherryPy.
• #12: mostly lifted from Ben Bangert’s Google Tech Talk presentation on Pylons and WSGI: http://www.groovie.org/articles/2006/09/18/wsgi-paste-pylons-and-all-that
• #13: Pylons includes Routes, also a Ben Bangert project; ported from Rails, but extended and moving in its own directions. Fairly popular outside of Pylons. Briefly compare versus CherryPy/Zope object publishing and Django's regular expressions. Pylons is agnostic, but SQLAlchemy is the overwhelming community favorite. Recipes are available for using Storm, Schevo (pure-Python, non-SQL DBMS), probably Geniusql, CouchDB Pylons default is the excellent Mako, developed by Michael Bayer as a derivation of Myghty's templating system. Buffet-compatible engines are easily swapped in, or used in tandem. This includes Genshi, Cheetah, Kid, Myghty, Jinja (Django-style). XML- or predefined tag-based versus Python-like syntax and inheritance model. Beaker (with Middleware). Caching supported in memory, filesystem and memcached. Signed cookies, and support for cookie-only sessions. FormEncode - validates and coerces to Python types. Touch on form generation / widget tools like ToscaWidgets, FormBuild, FormAlchemy. Helpers for common tasks like text operations (datetime formatting, Textile / Markdown), RSS, and form and URL tags. The latter require Routes and protect your templates from changes in URL structure. Also Javascript integration with Prototype and Scriptaculous, which may eventually disappear from WebHelpers.
• #14: In this case we can even show Pylons installation, and suggest it as a best practice Point out that QuickWiki basically uses the default Routes. We can look at more example Routes definitions when discussing map.resource and REST.
• #16: setuptools, PasteDeploy how an end user would install and run the app daemon mode, process management options 'entry points' facilitate plugin development Paste HTTP server thread-pooling substitute CherryPy's with one config file directive reverse-proxy with Apache, lighttpd, nginx, etc. Process control Monit, daemontools, supervisord, God
• #19: Debug in Wing: wingware.com&#x2014;paste-pylons <http://wingware.com/doc/howtos/paste-pylons> internationalization, and \"smart\" resources that might serve, say, XHTML and JSON
• #20: Although recall my concerns about the Law of Leaky Abstractions -- while Elixir may seem simpler, it may actually prove more complex to debug.