This post originated from an RSS feed registered with Python Buzz
by Carlos de la Guardia.
Original Post: Please Guido, pick me, pick me!
Feed Title: I blog therefore I am
Feed URL: http://blog.delaguardia.com.mx/feed.atom
Feed Description: A space to put my thoughts into writing.
If you are the developer of a Python web framework (I'm sure there must be thousands) and you haven't been reading your blogs lately, then if by any chance you happen to read this don't waste any more time, go and write down your most convincing arguments about how your framework is the best out there.
You see, the BDFL (yes, Guido himself, do I have to spell it out?) is looking for a web framework for his new job at Google. Just imagine if they select yours! You'll be famous, you can end the debate about which Python framework to choose with the simple words, "well, Guido chose mine". Even if that doesn't do it, you can add humbly that "I think it's used all around Google" and this should be enough to declare your framework the winner. Think about it, just the productivity and bandwidth savings of no more "which is the best python web framework" discussions would be huge, and all thanks to you.
But hurry up, many leading web framework developers are pleading their case and you don't want to be last. Django, TurboGears, Twisted, you name it, the guy behind it may already have spoken his piece, maybe even denigrated your very own framework (oh, yes, they would stoop that low, who wouldn't for web framework fame and immortality?), and here you are, wasting your time with my blog, of all things.
You may be surprised if Guido doesn't already know your framework, but these things happen, so write down your blurb, better safe than sorry. Don't forget to tell him how you already reviewed all of the existing Python web frameworks before deciding to write your own, this will bring you some credibility. Remember to state how your framework is the most 'pythonic' of the lot. Don't worry about defining 'pythonic' or trying to come up with reasoned arguments about why your framework is more 'pythonic'. Guido will now at a glance if this is the case by just looking at four lines of sample code.
One other thing, whatever you do, do not say the word XML near Guido's comments section, or he will fail your framework and maybe even you. If your template engine or configuration machinery uses or produces XML, omit the fact in your explanation and start writing a new XML-less templating engine or configuration machinery while Guido comes around to reading your post. Or you could try to convince him, as many have done, even though he clearly has stated that he doesn't want any XML. Perhaps you are articulate enough to show him that he really likes XML after all.
What? You are still here? Go away, don't lose another second! Time is of the essence. Oh, and if Guido chooses your framework, don't forget who gave you the tip.