public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Yao <ryao@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Sun, 29 Jul 2012 22:23:31 -0400	[thread overview]
Message-ID: <5015F023.1000903@gentoo.org> (raw)
In-Reply-To: <5015EDC2.202@gentoo.org>

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

On 07/29/2012 10:13 PM, Mike Gilbert wrote:
> This past weekend, the topic of the current state of Python 3 in Gentoo
> was raised once again in the #gentoo-dev IRC channel. Here's where we
> currently stand:
> 
> 1. Python 3.2 is installed by default on major arches due to its
> presence in the stage3 tarball.
> 
> 2. Python 2 is NOT installed by default as nothing in the system set
> actually depends on it.
> 
> 3. In most cases, users end up building and installing Python 2.7 as a
> dependency of some other package once they have their system set up.
> Users end up having two versions of Python installed.
> 
> This third point is the cause of some annoyance for several (many?)
> developers and users. In most cases, there really is no reason for a
> user to have two versions of Python installed; it is simply a redundant
> set of code. However, if you attempt to remove Python 3, portage will
> just pull it back on the next world upgrade unless you mask it.
> 
> I don't think this makes for a very good user experience. So, how can we
> change that?
> 
> As I see it, we need a way to avoid portage's overly optimistic upgrade
> mechanic. One way to do that is to drop the stable keywords on Python 3,
> but I feel that is dishonest; Python 3 itself is perfectly stable, so we
> should not force users to unmask it.
> 
> The other way that occurs to me (and others) is to rename
> dev-lang/python-3* to dev-lang/python3, treating it as an entirely
> separate package. I believe this has been proposed in the past, and I'm
> honestly not sure why it never gained traction. It would take some work,
> but we have already had a couple of non-python devs volunteer to help out.
> 
> We can work out the technical details in follow-up discussion.
> 
> Is anyone in favor or opposed to this package rename idea? Are there any
> better ideas?
> 

I have already setup a github repository we could use to make the
appropriate changes to the tree at our leisure:

https://github.com/gentoo/portage-devel

Then it should be possible to do this change with minimal disruption
once we are happy with what we have there.

Also, I am willing to help. :)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2012-07-30  2:25 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 [this message]
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
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=5015F023.1000903@gentoo.org \
    --to=ryao@gentoo.org \
    --cc=gentoo-python@lists.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