Re: Versioning Libraries

2004-12-03 Thread Richard Brodie
"Peter Hansen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Anyway, you're confusing "instability" (I hate that word, > it has connotations of unreliability, which aren't intended) > with "enhancement". The API gets changed, yes, but by > adding new things, almost never by remov

Re: Versioning Libraries

2004-12-03 Thread Peter Hansen
Richard Brodie wrote: "Peter Hansen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Python is exceptionally backwards compatible, so generally code from an older version will run unchanged on newer Pythons. I'm just curious: why exceptionally? I like Python for a lot of reasons but I

Re: Versioning Libraries

2004-12-03 Thread Simon Brunning
On Fri, 3 Dec 2004 11:03:58 -, Richard Brodie <[EMAIL PROTECTED]> wrote: > I'm just curious: why exceptionally? I like Python for a lot of > reasons but I wouldn't put API stability high on the list. > Not compared with a traditional language like C or Fortran, > anyway. Which languages go aro

Re: Versioning Libraries

2004-12-03 Thread Richard Brodie
"Peter Hansen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Python is exceptionally backwards compatible, so generally > code from an older version will run unchanged on newer > Pythons. I'm just curious: why exceptionally? I like Python for a lot of reasons but I wouldn't put A

Re: Versioning Libraries

2004-12-02 Thread Bryan
Peter Hansen wrote: Randall Smith wrote: As Python changes and old code still needs to work properly, I wonder if there is a standard way to note which version of the Python interpreter code is intended to work with. I know that an executable may begin with #!/usr/bin/python2.3 or something sim

Re: Versioning Libraries

2004-12-02 Thread Peter Hansen
Randall Smith wrote: As Python changes and old code still needs to work properly, I wonder if there is a standard way to note which version of the Python interpreter code is intended to work with. I know that an executable may begin with #!/usr/bin/python2.3 or something similar, but what about

Versioning Libraries

2004-12-02 Thread Randall Smith
As Python changes and old code still needs to work properly, I wonder if there is a standard way to note which version of the Python interpreter code is intended to work with. I know that an executable may begin with #!/usr/bin/python2.3 or something similar, but what about libraries and such?