As a programming noob, I've used both RailsTutorial's method (RoR/Git/Heroku), DjangoBook's Method (Py-Dj/no mention of version control/Apache+mod_python), and GAE's method.
I found RailsTutorial to be the easiest for my noobishness - though all were admittedly pretty good. GAE didn't seem easily portable at all compared to the other two - which was concerning, while DjangoBook's system seemed incomplete without teaching version control - like R-T does. For noobs, I like the easy way RoR/Git/Heroku are together, but I like Python better.
I'm anxious for http://www.Djangy.com to come out as the Heroku for Django and encouraged to see them use Git and not Hg.
It is an interesting conundrum right now. I am considering investing in using Ruby/Rails DUE TO Heroku. If djangy was ready and of comparable quality it would be an easy choice for me (I am comfortable in python, completely new to Ruby/Rails). But having to compare Heroku vs GAE vs Python-Stack is much more complex. I am not a fan of the limits in GAE, but I don't want to deal with system administration at this point. But I want to use python. Arg.
Yea, I feel like I'm in the same boat - only I'm the "business guy" at my startup so I do this to relax and learn about Python (which our code-base is mostly in).
HN member: endlessvoid94 is the guy behind Djangy - I hope he sees a lot of us begging for this!
I found RailsTutorial to be the easiest for my noobishness - though all were admittedly pretty good. GAE didn't seem easily portable at all compared to the other two - which was concerning, while DjangoBook's system seemed incomplete without teaching version control - like R-T does. For noobs, I like the easy way RoR/Git/Heroku are together, but I like Python better.
I'm anxious for http://www.Djangy.com to come out as the Heroku for Django and encouraged to see them use Git and not Hg.