John Fischer wrote:
> All,
>
> I am sponsoring this fast track for Laszlo (Laca) Peter from
> the JDS Desktop team. The case directory contains this proposal.
> I have set the timeout for Friday, August 29th, 2008.
>
> The project proposes to integrate Python 2.5 into a Patch release
> of Solaris. Python 2.5 and Python 2.4 will coexist on the system.
> The symbolic link pointing to the most recent version of python will
> be updated to point to Python 2.5.
>
> Thanks,
>
> John
>
>
Questions:
1) Does Python versioning "make sense" here? I.e. is Python 2.5 largely
compatible with 2.4, and is it the case that developers should start
using the new version? (Put another way, is there any reason that
developers should be building new programs against 2.4 after 2.5
integrates?)
2) Assuming that there are no surprises in the question above, wouldn't
it make more sense to upgrade 2.4 to "Uncommitted Obsolete" instead of
"Uncommitted"? (I.e. discourage new users from using 2.4 and direct
them to 2.5 instead.)
3) Is the project planning to undertake an effort to upgrade any Python
2.4 dependents delivered by OpenSolaris to Python 2.5? (Either as part
of this project, or as part of a follow on effort?)
Thanks. (FWIW, I think its unlikely that any answers to any of the
questions are going to negatively affect any decision to deliver Python
2.5. I'm more interested in what happens to Python 2.4, and what
precedent we might be setting, if any, when Python 2.6, 2.7... etc.
comes out.)
-- Garrett
