Stephen J. Turnbull wrote:
What that means to the architecture board is that they are going to have to write up some coding standards about globals, when you can create them, when you can touch them, what you can do when you do mess with them, what kind of cleanup is required, and how and where you must document all of the above when you do it. I'm not at all surprised that they throw up their hands and say "no, thanks".
From my experience, Python most effectively makes its way into organisations the way Linux did originally: developers are able to get approval to use it at a fairly low level because it doesn't cost anything, the licensing is more than reasonable and it will get the job done. Once it is in the door and being used for "support" tasks, it slowly makes its way closer and closer to core internal business applications (as different tasks come up, developers do initial
It's also the reason AppEngine cuts out a bunch of things to make it easier to keep apps under control:) prototypes in Python to try out functionality, then ask the obvious question "hey, how about we do the real thing in Python as well?"). Java and .NET have large organisations behind them with significant marketing budgets pushing them as the programming platform du jour. Python, like Linux before Red Hat started making money and the enterprise server hardware vendors got involved, relies more on word of mouth and unpaid advocacy. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia ---------------------------------------------------------------