public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Dirkjan Ochtman <djc@gentoo.org>
Cc: Richard Yao <ryao@gentoo.org>, gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Mon, 30 Jul 2012 11:06:54 +0200	[thread overview]
Message-ID: <20120730110654.1567cf84@pomiocik.lan> (raw)
In-Reply-To: <CAKmKYaCej=cEeS-yMQGNfmmHqGPHVMc79O8-v0cYEu+AAXyeOA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

On Mon, 30 Jul 2012 10:32:50 +0200
Dirkjan Ochtman <djc@gentoo.org> wrote:

> On Mon, Jul 30, 2012 at 10:23 AM, Richard Yao <ryao@gentoo.org> wrote:
> >> I've always thought renaming python-3 to python3 is
> >> faux-namespacing, and the thing SLOTs are supposed to help out
> >> with. Why aren't SLOTs helping us with this?
> >
> > Portage will attempt to upgrade software to a newer SLOT if it will
> > satisfy a dependency. This works when you cannot select versions via
> > eselect, but it causes problems when you can. There is no way to
> > tell it to prefer the selected version upgrades in other slots
> > unless the selected version cannot satisfy it.
> 
> Your last sentence fails to parse for me, perhaps expand one of the
> "it"s?
> 
> > I think that having to switch back would cause far less pain than
> > the current situation would, assuming that we ever do. If the python
> > developers refuse to make python 2.8, it is likely that someone
> > else will.
> 
> Please don't hope for a 2.8, it's simply not going to happen.
> 
> >> I agree that installing both is probably overkill for most users. I
> >> think the solution is somewhere outside the dev-lang/python
> >> package, though, in having the system set or portage or whatever
> >> the hell it is that first pulls in python prefer python-2.
> >
> > This would require amending the package manager specification.
> 
> Well, maybe we should explore that option. It would seem to solve a
> real problem that doesn't just apply to python. For example, the SLOT
> value could be prefixed with something to indicate that it should not
> be selected for upgrades automatically (i.e. other slots should be
> preferred).

[facepalm]

Or maybe we should explore the option of fixing python.eclass to not
depend on random python versions implicitly?

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-07-30  9:06 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30  2:13 [gentoo-python] Python 3 in Gentoo Mike Gilbert
2012-07-30  2:23 ` Richard Yao
2012-07-30  5:38 ` Rafael Goncalves Martins
2012-07-30  7:36 ` Dirkjan Ochtman
2012-07-30  8:23   ` Richard Yao
2012-07-30  8:32     ` Dirkjan Ochtman
2012-07-30  9:06       ` Michał Górny [this message]
2012-07-30  9:09         ` Dirkjan Ochtman
2012-07-30  9:16           ` Michał Górny
2012-07-30  9:23             ` Dirkjan Ochtman
2012-07-30  9:50               ` Michał Górny
2012-07-30 11:56                 ` Dirkjan Ochtman
2012-07-30 13:11                   ` Matthew Summers
2012-07-30 13:18                     ` Matthew Summers
2012-07-30 13:39                       ` Nikolaj Sjujskij
2012-07-30 14:05                         ` Jesus Rivero (Neurogeek)
2012-07-31  7:11                           ` Nikolaj Sjujskij
2012-07-31 12:09                             ` Ben de Groot
2012-07-31 12:14                               ` Nikolaj Sjujskij
2012-07-31 14:40                                 ` Ben de Groot
2012-07-31 16:46                                   ` Nikolaj Sjujskij
2012-07-30 14:00                     ` Jesus Rivero (Neurogeek)
2012-07-30 14:04                     ` Michał Górny
2012-07-30 14:07                       ` Matthew Summers
2012-07-30 14:11                         ` Michał Górny
2012-07-30 15:19   ` Mike Gilbert
2012-07-30 15:22     ` Dirkjan Ochtman
2012-07-30 15:30       ` Mike Gilbert
2012-07-30 15:40         ` Dirkjan Ochtman
2012-07-30 15:56           ` Mike Gilbert
2012-07-30 16:05             ` Matthew Summers
2012-07-30 16:16               ` Mike Gilbert
2012-07-30 16:20                 ` Matthew Summers
2012-07-30 16:53             ` Dirkjan Ochtman
2012-07-30 17:05               ` Mike Gilbert
2012-07-31 15:31                 ` Mike Gilbert
2012-08-08 21:07                   ` Mike Gilbert
2012-08-08 21:44                     ` Thomas Sachau
2012-08-08 22:09                       ` Jesus Rivero (Neurogeek)
2012-08-13 19:05                       ` Richard Yao
2012-08-13  9:46                     ` Dirkjan Ochtman
2012-08-13 19:07                     ` Richard Yao
2012-08-13 19:38                       ` Dirkjan Ochtman
2012-08-31  2:13                         ` Mike Gilbert
2012-09-02 12:21                           ` Thomas Sachau
2012-09-02 17:16                             ` Mike Gilbert
2012-09-02 17:34                               ` Michał Górny
2012-09-02 17:54                                 ` Mike Gilbert
2012-09-02 19:02                                   ` Michał Górny
2012-09-03 21:12                                     ` Mike Gilbert
2012-09-03 21:20                                       ` Michał Górny
2012-07-30 21:33     ` Thomas Sachau
2012-07-30  7:45 ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120730110654.1567cf84@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=djc@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=ryao@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox