Pyton 1.6's license

[Erno Kuusela]

>>>>> "Gregor" == Gregor Hoffleit <gregor at mediasupervision.de> writes:

    Gregor>  Then we had to remove all packages that might be
    Gregor> troublesome, license-wise. Among them are python-gdbm,
    Gregor> python-gtk, python-gnome, python-glade. 

it would seem atleast these are ok since they are under
the LGPL:

<URL:http://cgi.debian.org/cgi-bin/get-copyright?package=python-gtk>
<URL:http://cgi.debian.org/cgi-bin/get-copyright?package=python-gnome>
<URL:http://cgi.debian.org/cgi-bin/get-copyright?package=python-glade>

    Gregor> 2.) Stick with Python 1.5.2 and ignore Python 1.6 and up
    Gregor> until this issue is settled.

    Gregor>   The easiest solution. Many propose that.

(i'd like going straight to python 2.0 from 1.5.2 once it is released,
but this is irrelevant from the license discussion point of view)

    Gregor>   Anyway, if the issue is not settled in the near future,
    Gregor> that would more or less automatically mean a fork of
    Gregor> Python at some time, a VERY bad thing.

this is hardly realistic unless someone credible steps
up to maintain and develop it... [it might be hard to compete
with guido &co :) ]
  
    Gregor> 3.) Stick with Python 1.5.2 and package Python 1.6 as
    Gregor> optional packages (something like python1.6-base etc. pp.)
    Gregor> that could be installed parallel to Python 1.5.2.

    Gregor>   All existing packages would continue to depend on Python
    Gregor> 1.5.2, with no license trouble.

    Gregor>   Maintainers and users would have to decide if their
    Gregor> application/package is compatible with the new Python
    Gregor> license.

this would be good. particularly since the readline library
is under the GPL, lack of readline makes interactive mode of 1.6/2.0
pretty much unusable...

<URL:http://cgi.debian.org/cgi-bin/get-copyright?package=libreadline4>

  -- erno