I see your point. Why reinvent the wheel? True. But I'm not trying to re-do capistrano using python instead of ruby. Capistrano has been the spark that made me think about doing this, but that's all there is to Capistrano.
I'm doing this because: 1) I've anyways been thinking about this for ages. 2) I'd love to "djangostrano.py publish" or "djangostrano.py update-remote". 3) What about rails' migrations? It's *the* feature I've been dreaming of for django. What about "djangostrano.py new-evolution evolution_name"? And "djangostrano.py db-evolve"? 4) For the newbies: Learn python, django, then ruby and capistrano? Manually alter databases when schema evolves? Ugh... Learn python, django, and publish. Draft database modifications using python, and store them to make the database evolve. Sounds better IMHO :) 5) I prefer to write my recipes in python instead of adding another language to the mix. I already have to mangle python with all the frontend scripting and markup stuff. I'd love to keep it simpler. 6) I don't mind "reinventing the wheel" if it has any benefits, and the above are enough for me, though that's only a rough draft of what I've been working on. More to come. By the way. I don't try to tell anyone that "my tool's superior to tool X". I'm just letting the community know. Anyone to join my efforts? Gorgeous. Not? I'd love this kind of tool anyways. I'd be doing it alone, if that's the only way.
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
