[csw-maintainers] python question

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Walton wrote:
> Excerpts from Mike Watters's message of Thu Feb 05 12:00:35 -0500 2009:
>> I agree with Chad. we should have it all in one recipe in gar.
>> as far as when python3k becomes "python" that is a question there is no
>> clear answer to.  python3k is a complete re-write of python and very
>> little, if any, 2.X code will run on 3k.
> 
> But if 2.6 breaks lots of code too, making it the default could be
> problematic.  Does it have a 'behave like python < 2.6' flag?  If so,
> then that could work too.
> 
>> I would say we would be looking at "reviewing" the need for 2.x at a
>> minimum of a year after the python 2.X branch is terminated.
> 
> Yah, from what I read, there isn't a huge uptake of 3k yet...there
> should be lots of time to see how this shapes up and make a good
> decision when the time comes.
> 
> -Ben
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers

According to the Python folks 2.6.1 "does not" break existing code.
it will shoot warnings about the deprecated code being used but there is
a flag that can turn the warnings on and off


The following is an excerpt from the python page about python 2.6.1

- --- Begin Quote ---  http://docs.python.org/whatsnew/2.6.html

Author:	A.M. Kuchling (amk at amk.ca)
Release:	2.6.1
Date:	January 09, 2009

This article explains the new features in Python 2.6, released on
October 1 2008. The release schedule is described in PEP 361.

The major theme of Python 2.6 is preparing the migration path to Python
3.0, a major redesign of the language. Whenever possible, Python 2.6
incorporates new features and syntax from 3.0 while remaining compatible
with existing code by not removing older features or syntax. When it’s
not possible to do that, Python 2.6 tries to do what it can, adding
compatibility functions in a future_builtins module and a -3 switch to
warn about usages that will become unsupported in 3.0.

Some significant new packages have been added to the standard library,
such as the multiprocessing and json modules, but there aren’t many new
features that aren’t related to Python 3.0 in some way.

Python 2.6 also sees a number of improvements and bugfixes throughout
the source. A search through the change logs finds there were 259
patches applied and 612 bugs fixed between Python 2.5 and 2.6. Both
figures are likely to be underestimates.

This article doesn’t attempt to provide a complete specification of the
new features, but instead provides a convenient overview. For full
details, you should refer to the documentation for Python 2.6. If you
want to understand the rationale for the design and implementation,
refer to the PEP for a particular new feature. Whenever possible,
“What’s New in Python” links to the bug/patch item for each change.

- --- End Quote ---

- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmLIQwACgkQLrhmsXMSLxesuwCgiyGdQGTcnC73PqIg2QFuRCXf
Ik4AoJqC94Y1UvKJes1m45LlqNPgiz7c
=idhN
-----END PGP SIGNATURE-----