A day after TurboGears’ release

TurboGears had a quiet launch on Wednesday, when I presented the “20 Minute Wiki” live at the first MichiPUG meeting. It was listed as just “CherryPy+SQLObject” on the agenda, since TurboGears hadn’t been announced in any form at that point.

Yesterday, I made the more public announcement here on Blue Sky On Mars and on python-announce. From previous experience, it seemed like things tended to be a bit quieter on the weekends. It turns out that Python people were watching, even on Saturday. And, it also turns out that Python people are still very interested in web toolkits!

In a little more than a day, the “20 Minute Wiki” screencast has been viewed more than 1,000 times. That’s rather startling for my first screencast. By the way, I should take this opportunity to correct a problem with my screencast: I pronounced “MochiKit” wrong. Bob Ippolito pointed out that “mochi” is a Japanese word that is pronounced MOH-chee.

Bob, in addition to creating the fabulous MochiKit, also gets credit as the first person to submit code to TurboGears: a nifty snippet for doing Bonjour (formerly Rendezvous aka zeroconf) advertisements of the project you’re working on. Phillip Eby gets credit as the first person other than me to respond to a question on the TurboGears mailing list. I’m glad he did, because he was able to go into some detail about installing Python Eggs when you already have some of the packages installed.

On the TurboGears mailing list, it sounds like Windows and Mac users have been having good success with the Easy Install, but that Linux users have been having a harder time. ASAP, I’m going to write another install doc to deal with some of the complexities that can come up. Eggs are a great tool for Python and the solve a number of problems, so they’re well worth the little bit of extra trouble involved right now until they become the norm.

Out on the web, there were several blog posts talking about TurboGears. Bob said:

There’s a lot of good first impressions to be had with the technology

And he enumerated some of the reasons why I like the projects that I chose for TurboGears. As a Twisted fan (and contributor), he’d like to see it running behind Twisted. That would be difficult with SQLObject, which is synchronous, because Twisted is asynchronous.

Phillip said:

Okay, so TurboGears is cool. Not because it’s another Python web framework, but because it’s a… megaframework? Okay, so it’s not a framework, but what the heck is a megaframework?

Not that I have a better name for it, mind you. It is definitely a new thing in the Python world – a compelling project built almost entirely from separately-packaged Python components, powered by setuptools and EasyInstall.

EasyInstall is a key piece of technology to make something like TurboGears fly. If Phillip hadn’t created it (and done such a fine job of it!), I would have had to create some far less pleasant and less powerful mechanism to make TurboGears installable for people who don’t have an afternoon to waste tracking down dependencies.

It’s late for me now, so I’m going to have to continue checking out and commenting on the responses another time. I appreciate the early interest and I’m really excited about the parts that are yet to come!

8 thoughts on “A day after TurboGears’ release”

  1. You guys keep making this so hard on me! I finally decide that it’s time for me to learn how to create web apps, and settle on Django as I’m a long time Python guy.

    Then you create a brand new really cool-looking framework, creating new indecision for me!

    Oh well, I guess having to choose between really cool options is the kind of problem I can deal with.

  2. I did come across tada for the first time a few days ago. It looks neat, but I’m ultimately really turned off by the “callbacks everywhere” style of programming. I’ve gathered that the new Python 2.5 features may be able to alleviate that, and I would happily take another look.

  3. Oh, and I didn’t mean to skip over Jay’s comment above. I do agree that having more than one really good choice is better than having a couple of crappy choices.

    And I’m glad you think TurboGears is really cool looking!

  4. “Metaframework” would be a more accurate name for TurboGears, as it wraps several existing frameworks. It’s the same rationale than for Apple’s Metapackages which are aggregates of several installation packages.

    BTW TurboGears is *very* cool.

  5. While I can see the argument for “metaframework”, I chose “megaframework” to reflect the frontend-to-backend all-inclusive nature of it. I don’t think “meta” captures that as well.

    Glad you like TurboGears!

  6. How about a 20 minute video on how to launch the TG program after you’ve installed the rpm? After two days of beating my head against the wall and some googling, I discovered the

    tg-admin -c ::ffff:127.0.0.1

    trick. Geesh. I don’t care how cool it is, if thats what I have to do to load it 20 times a day it’s going to get real old, real fast.

  7. Sorry to hear that you had trouble getting the program (I assume you mean the Toolbox?) running. Did you try to mailing list? That’s usually the best place for help.

    I’ve never used the RPM personally… it may be worth adding a note to the docs:

    http://docs.turbogears.org/1.0/TgAdmin

    I assume the command is actually tg-admin toolbox -c ::ffff:127.0.0.1

Comments are closed.