Skip to main content

Pylons: first impressions

A couple co-workers and I spent some time with Pylons yesterday, enough to get to where we started to feel productive, but not much more than that. I think there's value in a newbie's first impressions, so here are mine. I'm sure at least some of these are wrong.
  1. Poor documentation of core Pylons (Mako and SQLAlchemy are fine -- thanks, Mike). I had to use the source several times. I'm still not really sure how Routes works, although I was mostly able to make it do what I wanted. The first tutorial overcomplicated things, showing how to configure things to handle semi-obscure requirements, without explaining those requirements or simpler alternatives.
  2. Helpful community. I got most of the answers I needed pretty quickly in the #pylons freenode IRC channel.
  3. Not much black magic: if you know Python you won't be struggling with weird Pylons-only concepts. It's all modules, classes, and dicts put together in an intuitive way (at least to my way of thinking).
  4. SA (SQLAlchemy) is an amazing pleasure to use. (Okay, not just in Pylons, but I had to say it.) I have a slightly unusual schema -- the details are outside my scope here -- and SA's autoload handled it perfectly.
  5. I wrote more CRUD boilerplate than I would have liked. There is no real alternative to Django's "admin app." DBMechanic looks like it's getting close, but it's TG-and-Genshi only for now. FormAlchemy is a partial solution (I did use it) but only does html generation; you'll still write boilerplate in your controllers.
  6. Genshi appeals to me in theory but in practice its XML nature makes it feel clunky. XInclude as an alternative to template inheritance? 3 lines of xmlns per template? Mako has its own verbosity problems, e.g., having to do a def to pass a title to the parent template, but these aren't inherent to Mako's approach the way they are to Genshi's (we're XML, dammit), and Mike seems mildy interested in improving this specific example for the next release.
  7. The pyfacebook tutorial is long on throwing wads of code at you and short on explaining what's actually going on. What does facebook.check_session() do? What does the facebook_middleware do? Why? Most facebook api tutorials have this same problem. Obviously I haven't written a better one, so call me a hypocrite, but tutorial authors, please explain the why and not just the what.

Comments

jacob said…
You mentioned django, what is the benefit to pylons vs django?

I am considering which 'framework' to jump in bed with, looking for input.

Best,
J
Jonathan Ellis said…
From my perspective, the main reason to use Pylons is that it's designed to work well with SQLAlchemy and Mako/Genshi, which are much better than the django ORM and templating engine.
Lijit_Dave said…
Thanks for the heads up, I'm just working my way up in python (system/shell scripts, sqlalchemy, and now web work) with a background in PHP and some experience w/Rails.

I generally dev on windows, so Pylons won the toss up because Zope didn't like my machine and I was in the mood to compile it ( just to find out if I like it or not)
John Brennan said…
I just stumbled on to your blog. I've been using Pylons for several months now and love it. Although PHP is still in my heart and I've been working in parallel with CakePHP which is another MVC.

Getting started with Pylons is pretty quick, but because it is so flexible, I found it hard to really make it my own. What I mean by that is adding authentication, building out the mako templates, etc.

After several discussions with the great fellows over at the pylons google group, I decided to put all my code online.

It's over at:
Zero to 60 with Pylons... in just minutes.

Popular posts from this blog

PyCon Python IDE review

I presented an IDE review at PyCon last Friday. It was basically a re-review of what I thought were the 3 most promising IDEs from the Utah Python User Group IDE review , to which I added SPE, which was by far the most popular of the ones we left out that time. The versions reviewed are: PyDev 1.0.2 SPE 0.8.2.a Komodo 3.5.2 Wing IDE 2.1 beta 1 I'd intended to base my presentation around a comparison of writing a smallish program in each of the IDEs, but the more I tried to make this not suck, the more I realized it was a losing proposition. Instead, I decided to try to focus on the features in each that most set them apart from the others (both positive and negative); this seemed more likely be useful. (I did a new feature matrix for this review, which is included after my comments. The slides I used are also up, at http://utahpython.org/jellis/pycon-ides.pdf , but aren't very useful absent video of the presentation itself. Hence this post.) PyDev PyDev has g...

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...

A review of 6 Python IDEs

(March 2006: you may also be interested the updated review I did for PyCon -- http://spyced.blogspot.com/2006/02/pycon-python-ide-review.html .) For September's meeting, the Utah Python User Group hosted an IDE shootout. 5 presenters reviewed 6 IDEs: PyDev 0.9.8.1 Eric3 3.7.1 Boa Constructor 0.4.4 BlackAdder 1.1 Komodo 3.1 Wing IDE 2.0.3 (The windows version was tested for all but Eric3, which was tested on Linux. Eric3 is based on Qt, which basically means you can't run it on Windows unless you've shelled out $$$ for a commerical Qt license, since there is no GPL version of Qt for Windows. Yes, there's Qt Free , but that's not exactly production-ready software.) Perhaps the most notable IDEs not included are SPE and DrPython. Alas, nobody had time to review these, but if you're looking for a free IDE perhaps you should include these in your search, because PyDev was the only one of the 3 free ones that we'd consider using. And if you aren...