Lonely Lion

Django 1.0 rc is coming this August, according to the RFC Jacob posted last night. Let’s keep our fingers crossed on that one, I’d love to see it happen.

I started my first AppEngine project this evening. I was lucky enough to get into the Beta. I don’t want to be too gushy or hyperbolic, but this is the future folks.

I’m not going to cover the bits about what appengine is, I’m assuming you’ve heard. If not, head over to the appengine site and do some reading. If you’re a little bit confused about WSGI, I encourage you to read anything Ian Bicking has written over the past few years, or my humble article on building a wsgi app.

So…my plan is to build a tomato tracking application on top of THE CLOUD (cue the music). The wife and I are planting a bunch of tomatoes this year, so I’m sort of hopped up on them. The app will let folks to report on the life, well being, and eventual yields of their backyard tomatoes. It’s going to be the world’s greatest web application. I’m going to develop it before a live studio audience via the TomatoBase Google Code Project. The app will live at http://tomatobase.appspot.com.

So far, there’s not much there. Just a landing page that says something pithy, that’s protected by a Google user login. I initially thought I’d jump feet first into the Google themed stack, using their very fancy webapp api, but after reading how easy it is to just go for Django, I decided to go with what I know. There’s a few gotchas, it’s really more like Django-Lite, but it’s still pretty darn good. You lose the ORM and Admin, but still get the url mapper, controllers, middleware, templates…oh, and BigTable. Pretty good trade as far as I’m concerned.

Developing with the toolkit is pretty slick, everything runs locally until you’re ready to push, and then it’s a quick “appcfg.py update django-mater” and it goes live. So simple. I love it.

I haven’t really ventured beyond exploration into actual TomatoBase development just yet. I started exploring the user system a bit, it’s pretty straight-forward. So straight-forward that I contributed a decorator to Django Snippets that lets you use the user system in a @loginrequired sort of way. It’s here: Google AppEngine Login Decorator.

I’m moving much quicker on this than I anticipated. I thought I wouldn’t have time to explore until this weekend, but it’s a really compelling product. I’m excited for them to open it up to a wider audience. At some point I’ll write a bit about what I think this all means (this means something), but for now I’m too busy playing.

It was only a matter of time. Great great great!

At the state of Django talk on Saturday at Pycon, I asked what the status of Django on Jython was, as I think for guys like me (trying to explain Python and Django to traditional JVM-happy shops) that stack is going to get some traction. If I can tell someone that my crack team of consultants can build a full featured web application in record time, and deploy it in their existing JVM heavy infrastructure, I’ll turn some heads.

If I can turnaround and say, the exact same app will also run in your .NET infrastructure, now the heads are spinning off into the cosmos.

Python for the win!

Simon Wistow asks whether or not we need a better open source queuing system. My answer is yes. I’ve built two one-off hackish queuing systems for $work in the past three years, both of which used database tables as queues, both of which were only accessible by a language-locked api, neither of which was accessible by any sort of neutral service. Both had very specific tasks, hold tasks in a queue for offline (read: outside of a web transaction) processing.

Both jobs could have been fulfilled by a nice message queue service, but it didn’t seem like the effort was worth the payoff. That said, now that I’ve built two of exactly the same thing, I’m 100% of the belief that I’d love to have a easy to install web service-y queue (that isn’t owned by Amazon).

So, why the need? It’s sort of like the evolution of CouchDB & friends I wrote about back in December, all web programmers eventually are expected to be programmers, then they start examining the tools the traditionalists have built, and they question, “why can’t this be better?” Relational databases might not be best for web apps (I’m still not convinced, but for the sake of argument, go for it.) Full featured queue services might not be best for web apps. If for no other reason than they introduce a complicated system into your ecosphere for what is actually a very simple problem. I like Simon’s pointing at memcache and saying, “make a queue that works like that.” That would be pretty cool. I’m voting +1.

That said, like a good American I’m making this vote without fully examining all the candidates. Maybe the existing queues are simple enough…educate me lazy-web.

So, PyCon is over (for me). I wasn’t able to participate in the sprinting this year, probably a good thing as too many late nights make me cranky. All in all, I had a great PyCon, met a lot of interesting folks, learned some new stuff, and had a lot of fun. The sessions I attended were good, but the BoF’s really stand out for me this year. Especially the Netflix BoF and the follow-up data-visualization BoF. Both were small (+! Small BoF’s FTW!) and really got me thinking.

The conference itself was really well managed. Things ran smoothly, people mingled, sandwiches were eaten, and talks were given. Friday and Saturday night were both pretty late and beery, yet again proving that I’m 31 and have baby. My rockstar genes have seriously been damaged by fatherhood. As an aside, I’ve been giving a after-several-beers rant about how MySpace is the greatest thing since representative democracy for so long now that Atul Varma finally cut off further discussion until I blog the speech. It’s a pretty good speech, I’m not sure it’ll survive the light of day, but I’ll work on it soon.

The best part of PyCon, in my esteemed opinion, is the people you meet. I finally got to talk to Mike Bayer, whom I’ve often pointed out as “the most prolific Python library writer ever.” I’ve been a fan of Data Wrangling for a while, and had the chance to talk to its steward Pete Skomoroch. He led the Netflix BoF, and his colleague Chris Gemignani led the data visualization BoF. They work for Juice Analytics, which seems to be doing some really interesting work.

PSC (whom I work for), was a sponsor this year. We had some good conversations with people at our booth, and sponsored a dinner Friday night. It was sort of our coming out party, as we’ve been working pretty hard (though quietly) for the past year to establish a solid Python based consultancy within a 100 person IT firm. PSC has been around for 17 years, has a great group of traditional manufacturing clients, and has never been unprofitable. They saw opportunities in the Python world, and hired me last year to help build a team. We’re 7 developers strong as of this morning. That, coupled with 1040 attendees at PyCon this year (up from 600 in 2007) says to me that Python is really building a market here in Chicago and elsewhere. It’s an exciting time to be a Python developer.

Anywho, great PyCon this year folks…looking forward to next year already.

It’s started. We stuffed a thousand bags with thirty volunteers and seven pizzas. (Yes, it sounds like the volunteers and pizzas were stuffed into the bags, I realize this after having already written in. It’s a shame my backspace key is totally broken, so I can’t fix it. Also, it’s funny sounding.)

Anywho, Pycon is on! Hurray for Pycon!

I wrote a short article on writing Excel files with Python and exporting them with Django on developer.com. The site caters to a (mostly) Java and .NET crowd, but they’re expanding into Python and Ruby. I’m going to try and write an article or two a month for them. I’ll link to them here. The topics will probably be a little bit basic for the regular Python crowd, the goal is to bring some new folks into the fold.

I’ve been treading water this week, and haven’t been keeping up with the blogosphere.

So, I’m behind, but wanted to link to Everyblock…you know…so it’s linked.

Really great stuff, congrats Blockheads.

Register now for early bird prices.

Chicago! Hurray!

Thanks to Brian Ray for making it happen.