Python 2.1 out
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! as Python 2.1 is out, there is no need to keep Python2 and Python152 in Debian, I think. it looks like 2.1 has GPL-compatible license (it has, in fact, three licenses) and code-breakage features like nested scopes are disabled by default. am I right? what do you think? miro -BEGIN PGP SIGNATURE- Version: PGP 7.0.4 iQA/AwUBOtxGOfQpPA/ctNXOEQK/3wCfcaQK2EGcAR+hsMVa9m0oaC9JnQgAmwdD 6pvCpmkWw7Wzj9HI1rABb3B1 =jEBn -END PGP SIGNATURE-
Re: Python 2.1 out
On Tue, Apr 17, 2001 at 03:33:45PM +0200, Vasko Miroslav wrote: > as Python 2.1 is out, there is no need to keep Python2 and Python152 > in Debian, I think. > > it looks like 2.1 has GPL-compatible license (it has, in fact, three > licenses) Thanks for pointing out the changes in LICENSE. Since there wasn't any big noise lately, I thought they had postponed any actions after 2.1. Short analysys: While Python 2.0 was based on the Python 1.6 codebase (which had a license that was incompatible with the GPL according to the FSF), Python 2.1 is now based on Python 1.6.1, which has a modified license. According to RMS the 1.6.1 license allows derived works which are compatible with the GPL. I'm not completely sure, though, if the license of this derived work (Python 2.1) already is accepted by the FSF as compatible with the GPL. The interesting part seems to be paragraph (7) of the new PSF license. I'll send a mail to RMS and ask for his comment. Gregor > and code-breakage features like nested scopes are disabled by default. > > am I right? > what do you think?
Re: Python 2.1 out
Vasko Miroslav wrote: > as Python 2.1 is out, there is no need to keep Python2 and Python152 > in Debian, I think. > [snip] > and code-breakage features like nested scopes are disabled by default. Licenses aside, there are the same technical issues with Python 2.1 as with Python 2.0. The byte code files are incompatible, and so are binaries of extension modules written in C. There could not be a full migration of Debian to Python 2.1 until all extensions have been rebuilt and tested successfully with 2.1. It could also take some time before developers of python-based packages (Zope etc) declare them to be compatible with Python 2.1. I expect this means that Python 1.5.2 will be around for a while yet. -Steve -- Steve Purcell, Pythangelist Get testing at http://pyunit.sourceforge.net/ Any opinions expressed herein are my own and not necessarily those of Yahoo
Re: Python 2.1 out
On 18-Apr-2001 Gregor Hoffleit wrote: > On Tue, Apr 17, 2001 at 03:33:45PM +0200, Vasko Miroslav wrote: >> as Python 2.1 is out, there is no need to keep Python2 and Python152 >> in Debian, I think. >> >> it looks like 2.1 has GPL-compatible license (it has, in fact, three >> licenses) > > Thanks for pointing out the changes in LICENSE. Since there wasn't any big > noise lately, I thought they had postponed any actions after 2.1. > last I checked it only helped derivatives of python, not python itself.
Re: Python 2.1 out
On Wed, Apr 18, 2001 at 08:26:00AM -0700, Sean 'Shaleh' Perry wrote: > > On 18-Apr-2001 Gregor Hoffleit wrote: > > On Tue, Apr 17, 2001 at 03:33:45PM +0200, Vasko Miroslav wrote: > >> as Python 2.1 is out, there is no need to keep Python2 and Python152 > >> in Debian, I think. > >> > >> it looks like 2.1 has GPL-compatible license (it has, in fact, three > >> licenses) > > > > Thanks for pointing out the changes in LICENSE. Since there wasn't any big > > noise lately, I thought they had postponed any actions after 2.1. > > > > last I checked it only helped derivatives of python, not python itself. Pardon me, but then couldn't we just release a derivative of Python, e.g. "Dython", change a few things, so that it is a true derivative, and then this might be compatible with the GPL ? I don't understand this... The LICENSE file in 2.1 seems to imply that the license issues with the FSF could be settled, but I'm currently trying to get a word from RMS on this. Gregor
Re: Python 2.1 out
Steve Purcell <[EMAIL PROTECTED]> writes: > Licenses aside, there are the same technical issues with Python 2.1 > as with Python 2.0. Python 2.1 seems to print some diagnostic messages during run-time; this might affect scripts which are invoked in cron jobs.
Re: Python 2.1 out
On Wed, Apr 18, 2001 at 10:25:52PM +0200, Florian Weimer wrote: | Steve Purcell <[EMAIL PROTECTED]> writes: | | > Licenses aside, there are the same technical issues with Python 2.1 | > as with Python 2.0. | | Python 2.1 seems to print some diagnostic messages during run-time; | this might affect scripts which are invoked in cron jobs. Are you sure they aren't warnings regarding code that will not work as expected in future versions? -D
