From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python 3.1 safe as default python?
Date: Sun, 2 Aug 2009 17:26:25 +0100 [thread overview]
Message-ID: <20090802172625.06f1db66@krikkit.digimed.co.uk> (raw)
In-Reply-To: <7284e2210908020817g1015ed0aw3086d32d7936e1a4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Sun, 2 Aug 2009 11:17:22 -0400, Doug Hunley wrote:
> I noticed that my 'emerge world' wants to replace python 2.6.2 with
> python 3.1 (I run ~x86). Is it safe to do so or will portage (and
> everything else) freak out? If it is, in fact, safe are there any
> extra (special) steps needed to ensure continued operation of things?
t does not replace python 2.6, it installs in a separate slot. Python 2.6
remains the default as many modules don't yet work with 3.
This is given in the elog message, but of course you have to be
brave/foolish enough to emerge it to see that. So yes, it is safe to
allow python 3.1 to install.
--
Neil Bothwick
I thought I saw the light at the end of the tunnel...
but it was just some sod with a torch bringing me more work!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-08-02 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 15:17 [gentoo-user] python 3.1 safe as default python? Doug Hunley
2009-08-02 16:25 ` [gentoo-user] " Nikos Chantziaras
2009-08-02 16:26 ` Neil Bothwick [this message]
2009-08-02 16:46 ` [gentoo-user] " Albert Hopkins
2009-08-02 17:20 ` [gentoo-user] " Christer Ekholm
2009-08-02 21:07 ` Keith Dart
2009-08-02 23:35 ` Doug Hunley
2009-08-03 0:01 ` Dale
2009-08-03 0:17 ` Mike Kazantsev
2009-08-03 0:35 ` Neil Bothwick
2009-08-03 0:15 ` Adam Carter
2009-08-03 0:27 ` Christer Ekholm
2009-08-03 5:09 ` Keith Dart
2009-08-03 0:28 ` Mike Kazantsev
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=20090802172625.06f1db66@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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