Re: Python 2.1 out

[Carey Evans]

Tom Cato Amundsen <[EMAIL PROTECTED]> writes:

> Excuse me for bugging you about this, but has you heard anything
> from RMS yet?  With the upcoming freeze, it would be nice to know as
> soon as possible if we will have a GPL compatible python 2.x in
> woody.

Actually, it'd be nice just to have Python 2.1 in woody before the
freeze, whether or not it's GPL compatible.  Or even get more Python
1.5 packages built for Python 2.0 as well.

Is there anything I can do myself to help with the Debian Python
packages?

-- 
 Carey Evans  http://home.clear.net.nz/pages/c.evans/

"Quiet, you'll miss the humorous conclusion."

Re: Python 2.1 out

[Neil Schemenauer]

Carey Evans wrote:
> Tom Cato Amundsen <[EMAIL PROTECTED]> writes:
> 
> > Excuse me for bugging you about this, but has you heard anything
> > from RMS yet?  With the upcoming freeze, it would be nice to know as
> > soon as possible if we will have a GPL compatible python 2.x in
> > woody.
> 
> Actually, it'd be nice just to have Python 2.1 in woody before the
> freeze, whether or not it's GPL compatible.  Or even get more Python
> 1.5 packages built for Python 2.0 as well.

Guido has recently checked in a license change that makes Python
GPL compatible.  That was confirmed by RMS and his laywer.  This
change will go into the 2.0.1 and 2.1.1 maintenance releases as
well as 2.2.  I'm not sure if 2.0.1 will be out before the
freeze.  Moshe should know.  I think he's on this list.

  Neil

Re: Python 2.1 out

[Florian Weimer]

Neil Schemenauer <[EMAIL PROTECTED]> writes:

> Guido has recently checked in a license change that makes Python
> GPL compatible.

Here's the diff:

Index: LICENSE
===
RCS file: /cvsroot/python/python/dist/src/LICENSE,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- LICENSE 2001/04/13 19:41:28 1.15
+++ LICENSE 2001/05/04 18:49:06 1.16
@@ -76,22 +76,11 @@
 6. This License Agreement will automatically terminate upon a material
 breach of its terms and conditions.
 
-7. This License Agreement shall be governed by the federal
-intellectual property law of the United States, including without
-limitation the federal copyright law, and, to the extent such
-U.S. federal law does not apply, by the law of the Commonwealth of
-Virginia, excluding Virginia's conflict of law provisions.
-Notwithstanding the foregoing, with regard to derivative works based
-on Python 2.1 that incorporate non-separable material that was
-previously distributed under the GNU General Public License (GPL), the
-law of the Commonwealth of Virginia shall govern this License
-Agreement only as to issues arising under or with respect to
-Paragraphs 4, 5, and 7 of this License Agreement.  Nothing in this
-License Agreement shall be deemed to create any relationship of
-agency, partnership, or joint venture between PSF and Licensee.  This
-License Agreement does not grant permission to use PSF trademarks or
-trade name in a trademark sense to endorse or promote products or
-services of Licensee, or any third party.
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between PSF and
+Licensee.  This License Agreement does not grant permission to use PSF
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
 
 8. By copying, installing or otherwise using Python 2.1, Licensee
 agrees to be bound by the terms and conditions of this License



[GPL compatibility]

> That was confirmed by RMS and his laywer.

The PSF license is compatible with the GPL, however, the CNRI license
still contains the problematic GPL-incompatible jurisdiction clause.
So better be careful.