Home Original page

[snake-farm] Re: 2.2.x backports of 2.3.x new features?

Laura Creighton lac at strakt.com
Wed Dec 11 11:50:09 EST 2002 
> Basically, in my understanding, PIAT will give the business developer 
> these features:
> 
>    1. same core-language version for an extended period of time (e.g. 18
>       months)
>          1. extension modules (particularly in-house and/or proprietary
>             third-party ones) don't need to be recompiled (often not an
>             option for proprietary third-party modules)
>          2. no change to semantics of valid code
>          3. no new syntax/keywords
>          4. within reason, what works with the core should keep working
>             with it as long as the PIAT version is the same (18
>             months+), with the exception of dependencies of bugs
>    2. library of tested modules/packages which are known to work with
>       the core-language version
>          1. precompiled binaries for the various (common) open-source
>             extension modules
>                1. compiled against the stable core-language version of
>                   Python
>                2. tested agains the stable core-language version of Python
>          2. the standard library of the core version (e.g.
>             standard-library 2.2)
>          3. (in this case) modules back-ported from later versions (e.g.
>             standard-library 2.3)
>          4. third-party modules not part of the standard library
>             (standard-library 2.3 could be considered a member of this set)
>          5. whereever possible, modules in the library should work with
>             all PIAT versions of the same release (that is, if there's a
>             module made available, it should work with 2.2.n, 2.2.n+1,
>             2.2.n+2, ... 2.2.m where n is the first PIAT version of 2.2
>             and m is the last), in other words, users aren't forced to
>             upgrade the core just to get a library updated _unless_ the
>             update to the library actually relies on a _bug fix_ in the
>             core.
> 
> But as I'm not a Python-in-a-Tie member, I'll let them respond 
> authoritatively,
> Mike

You could change that <wink>.  Get ready to be suggested for the
job of 'official spokesman' as well, since you have just demonstrated
competance for the position <grin> ....

was-that-the-roadrunner-I-just-saw-zipping-away-to-the-horizon-or 'ly
Laura Creighton
More information about the Python-list mailing list