Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-python
Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Sjujsckij Nikolaj <sterkrig@...>
From: Dirkjan Ochtman <djc@g.o>
Subject: Re: Bug 375257: python and >=linux-3 don't play well
Date: Thu, 22 Sep 2011 11:10:13 +0200
On Wed, Sep 21, 2011 at 21:38, Sjujsckij Nikolaj <sterkrig@...> wrote:
>  But when Linux 3.x goes stable, stable Python versions suddenly became
> "broken".

Well, only versions of Python built *after* you start using the new kernel.

> I don't think it's reasonable to have Python 2.4-2.6 in Portage tree
> keyworded stable (and therefore considered to be supported) and know for
> sure that it's just a matter of time when somebody have to recompile it and
> boom! half of Python modules stop working. I daresay these cases should be
> handled too.

Well, I wouldn't say half of Python modules, but I agree that we
should probably revbump the others, too.

Cheers,

Dirkjan


Replies:
Re: Bug 375257: python and >=linux-3 don't play well
-- Michał Górny
Re: Bug 375257: python and >=linux-3 don't play well
-- Sjujskij Nikolaj
References:
Bug 375257: python and >=linux-3 don't play well
-- Dirkjan Ochtman
Re: Bug 375257: python and >=linux-3 don't play well
-- Matthew Summers
Re: Bug 375257: python and >=linux-3 don't play well
-- Sjujsckij Nikolaj
Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Bug 375257: python and >=linux-3 don't play well
Next by thread:
Re: Bug 375257: python and >=linux-3 don't play well
Previous by date:
Re: Bug 375257: python and >=linux-3 don't play well
Next by date:
Re: Bug 375257: python and >=linux-3 don't play well


Updated Jun 01, 2012

Summary: Archive of the gentoo-python mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.