Hi,
Ok, I have read that too. 2.1.1 (and 2.0.1) are officially GPL
compatible.
I would be nice to have all Python related packages depend on a specific
python version (Depends: python-base (>= 1.5.2), python-base (<< 2.0)),
because with the current approach for Python in Debian there can be only
Sorry guys for the silence. I had to go through upgrading my hardware,
upgrading my line setup to a new provider with a flat fee, and finally, some
real world work kept me busy.
On Mon, May 21, 2001 at 10:35:15PM +0200, Tom Cato Amundsen wrote:
> On 21 May 2001 20:57:34 +0200, Matthias Klose wrot
On Mon, May 21, 2001 at 01:12:57PM -0700, Neil Schemenauer wrote:
> Gordon Sadler wrote:
> > I'd just like to comment on this. I installed python2.1 some time ago in
> > /usr/local. However this leads to problems. You have to modify some of
> > the code (eg PYTHONPATH IIRC) due to using prefix=/usr
On 21 May 2001 20:57:34 +0200, Matthias Klose wrote:
> I really would like to see 2.1 in the next Debian release. I'd like to
> ask Gregor (the maintainer) for an upload schedule, so that other
> maintainers can rely on this to get their packages ready for the next
> release as well. Are there sti
Gordon Sadler wrote:
> I'd just like to comment on this. I installed python2.1 some time ago in
> /usr/local. However this leads to problems. You have to modify some of
> the code (eg PYTHONPATH IIRC) due to using prefix=/usr/local.
Which code is "the code"? The code distributed with Python works
On Mon, May 21, 2001 at 12:14:07PM -0700, Neil Schemenauer wrote:
> Matthias Klose wrote:
> > - new packages names python2.1-foobar
> >
> > - same package names, but add versioned dependencies: python-foobar (>= 2.1)
> >
> > The latter will cause some incompatibilities until all python2
> > depen
Matthias Klose wrote:
> - new packages names python2.1-foobar
>
> - same package names, but add versioned dependencies: python-foobar (>= 2.1)
>
> The latter will cause some incompatibilities until all python2
> dependent packages are uploaded for 2.1.
I strongly prefer the latter. If people wa
ok, python-2.1. was released some time ago. When and how will it
appear in unstable?
IMO it doesn't make sense to support python2.0 AND python2.1 in
unstable. Therefore I propose to drop 2.0 in unstable and upload
2.1. There seem to be two ways how this can be done:
- new packages names python2.1
8 matches
Mail list logo
