How to sell Python ( and OpenSoruce )
Richard Brodie
R.Brodie at rl.ac.uk
Thu Jun 22 12:53:29 EDT 2000
"RickZ" <rzantowNOrzSPAM at usa.net.invalid> wrote in message
news:03bf34ab.667a04d2 at usw-ex0105-040.remarq.com...
> I'd like to get my employer to add Python to its "approved" list
> of development tools, too. But which Python? It's an extra
> handicap to say, "Well, the language now is changing constantly
> in ways that will potentially break what we develop now. And I
> am not at all sure what it will look like at this time next
> year.
I don't think you can consistantly say that about Python but not
Java. There was the bug AWT/Swing thing, and various other
deprecated features.
I think you are making too much of the incompatible change thing.
It's much easier to drop features where you have control of the
source: the fact that, with Python possible, compatibility problems
get discussed in public early on in the development cycle shouldn't
be seen as a problem.
You can always freeze the version you are using on the production
machines. Regression testing on N different JVMs isn't going to be
any easier.
More information about the Python-list
mailing list