Re: Proposal: Reorganizing Python for Python 2.0
What I want is if we allow both Python 1.5 _and_ Python 2.0 to be installed simultaneously we also must allow to actually use both at the same time. I want to do both #python15 -c "import sys" and #python20 -c "import sys" Or, I want to switch my alternative settings for the Python interpreter from 2.0 to 1.5 and in this case I want all python applications to work like before, but with the changed Python interpreter. So we need 1) a directory where all source .py modules are put into, for example /usr/lib/pythonsrc. In this directory we have subdirs for a) compatible source for 1.5 and 2.0 b) only 1.5, not 2.0 c) only 2.0, not 1.5 2) a directory where all compiled .py[co] modules are put into, for example /usr/lib/python. In this directory we have subdirs for a) compiled bytecode for 1.5 b) compiled bytecode for 2.0 Whats the good thing about this: Python applications put their source into /usr/lib/pythonsrc. Then they compile for all available Python interpreters (for example 1.5 and 2.0) and put the compiled files in /usr/lib/python/x.x This way all applications work with all installed Python interpreters, they dont need wrapper scripts (but an application that works on Python 2.0 only has to call the /usr/bin/python20 interpreter of course). And a final thought: why dont we replace Python 1.5.2 with 2.0 and save us all this hassle with Python versions? I dont think that there are Python apps that only work on 1.5, but not on 2.0. Bastian Kleineidam pgp4WpCPLkN4e.pgp Description: PGP signature
Python license and GPL programs
Hello, I followed the discussion of the Python 2.0 packaging. In the python2-base package I saw this text: Note that the license of Python 2 is not compatible with the GNU General Public License (cf. clause 6 of the new Python license). Please don't use GPL code with Python2 without asking the authors of the GPL code for their explicit permission. I am distributing Python programs under the GPL. So is this sentence above telling me that all users are not allowed to use my GPLed programs with Python 2.0?? What about previous versions? What is a possible solution? Use LGPL? Or restrict usage to Python <<2.0? Bastian Kleineidam pgpLQpndwquHz.pgp Description: PGP signature
Re: Examples of making *.pyc files in postinst
On Tue, Jan 23, 2001 at 11:27:47PM +, Francis Irving wrote: > I can't find these examples anywhere! They aren't in that directory, > in any package in the Debian archive. Look in /var/lib/dpkg/info/python-base.postinst. The 'locate' command can scan for files. Bastian pgpEWgZRCsMuZ.pgp Description: PGP signature
Python 2.x and GPL (official blurb form 2.1a1)
Hi all, I just leeched the new Python 2.1 alpha 1 release and discovered this comment on GPL-incompatibility: [...] After Python 2.0 was released by BeOpen.com, Guido van Rossum and the other PythonLabs developers joined Digital Creations. The intention is for all intellectual property added from this point on to be owned by the Python Software Foundation (PSF), a non-profit that will be created modeled after the Apache Software Foundation. We will also attempt to get the ownership in previous versions transferred to the PSF, and straighten out the license to remove the GPL-incompatibility introduced by CNRI's Python 1.6 license. In the interim, Guido van Rossum will own all new intellectual property, and no new license is added. [...] So it seems that 2.1 will be GPL compatible :) That is also an official answer to my previous concern: Python 2.0 and 1.6 are not GPL compatible. Hrmpf. Bastian pgprL8CiN6rmx.pgp Description: PGP signature
Re: Python modules to be recompiled for Python 2.0
Jérôme, On Tue, Feb 20, 2001 at 01:45:05PM +0100, Jérôme Marant wrote: > I do maintain 2 python modules : > . python-xml, xbel and xbel-utils > . python-unit > > Are there people interested in using them with Python2 ? Yes, I am using python-xml. Bastian pgpnz9kGaMTGQ.pgp Description: PGP signature
Re: Proposal: Reorganizing Python for Python 2.0
Hello, > * we make /usr/bin/python point to python 2 thanks to alternatives > * we run a compileall.py in python/site-packages in order to > get them byte-recompiled for 2.0 From the Python news file: - Python bytecode files (*.pyc and *.pyo) are not compatible between releases. Now what if you install Python 2.0 and then call /usr/bin/python15? This will use the newly-compiled .pyc files which are incompatible. Bastian Kleineidam pgpspm0KOHy2K.pgp Description: PGP signature
