public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Stabilization of Python 3.1
Date: Sun, 20 Sep 2009 17:24:53 +0200	[thread overview]
Message-ID: <200909201725.00070.Arfrever@gentoo.org> (raw)
In-Reply-To: <19e69baf3d2d95babe2abc5f89c4322d@localhost>

[-- Attachment #1: Type: Text/Plain, Size: 1958 bytes --]

2009-09-20 16:53:37 Jesús Guerrero napisał(a):
> On Sun, 20 Sep 2009 00:41:32 +0200, Dawid Węgliński <cla@gentoo.org>
> wrote:
> > On Sunday 20 of September 2009 00:32:28 Dale wrote:
> >> >
> >> > ~arch is for testing ebuilds, not the upstream package
> >>
> >> So it would be OK to mark something "stable" even tho portage itself
> >> doesn't work with it?  Sorry, this makes no sense to me.  I run stable
> >> for the most part and having a package that portage depends on that is
> >> not stable just sounds a little like putting the cart before the horse.
> >>
> >> See some of the other replies as to why this is a not so good idea.
> >>
> >> Dale
> >>
> >> :-)  :-)
> > 
> > You mix it up. Portage works with python 3.1. If an user switches to
> > python 
> > 3.1 as the main interpreter, it's possible that his own scripts won't
> > work. 
> 
> Yes?
> 
> # eselect python set 2
> # emerge -s foo
>   File "/usr/bin/emerge", line 41
>     except PermissionDenied, e:
>                            ^
> SyntaxError: invalid syntax
> 
> 
> Ummm, yes, it works *beautifully*, you see. Nothing else to add.

I have fixed it today :) .
http://sources.gentoo.org/viewcvs.py/portage?rev=14289&view=rev

> > Marking it stable sometine in november give's some time to ebuilds 
> > maintainers to fix their python based apps just like it's done with gcc 
> > stabilization.
> 
> That's not the usual case. In Gentoo we have a serious policy of not
> marking as stable things until it has passed one month without any serious
> bug report about it.

There wasn't any serious bug report about Python 3.1.
IIRC the only problem was a (already fixed) build failure caused by non-UTF-8
characters in header of Berkeley DB.
Stabilization of Python 3.1.1-r1 is planned over 1 month after its addition to
the tree and about 3 months after addition of 3.1 slot to the tree.

-- 
Arfrever Frehtes Taifersar Arahesis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-09-20 15:23 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 16:48 [gentoo-dev] Stabilization of Python 3.1 Arfrever Frehtes Taifersar Arahesis
2009-09-19 16:53 ` Dirkjan Ochtman
2009-09-19 17:06 ` Alex Legler
2009-09-19 17:09   ` Dirkjan Ochtman
2009-09-19 17:21     ` Dale
2009-09-19 17:28       ` Olivier Crête
2009-09-19 22:32         ` Dale
2009-09-19 22:41           ` Dawid Węgliński
2009-09-20 14:53             ` Jesús Guerrero
2009-09-20 15:16               ` Dale
2009-09-20 15:24               ` Arfrever Frehtes Taifersar Arahesis [this message]
2009-09-20 15:28                 ` Jesús Guerrero
2009-09-20 17:30                 ` Nirbheek Chauhan
2009-09-20 17:57                   ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 22:15             ` Mark Loeser
2009-09-20 22:47               ` Dale
2009-09-20 11:18         ` Richard Freeman
2009-09-20 14:51           ` Dale
2009-09-19 17:33       ` [gentoo-dev] " Nikos Chantziaras
2009-09-19 17:26     ` [gentoo-dev] " Alex Legler
2009-09-19 18:24       ` AllenJB
2009-09-19 18:20     ` AllenJB
2009-09-19 18:59       ` Arfrever Frehtes Taifersar Arahesis
2009-09-19 19:50         ` Petteri Räty
2009-09-19 20:21           ` Robert Bridge
2009-09-19 23:29             ` Alex Alexander
2009-09-20 10:35               ` Petteri Räty
2009-09-20 20:33                 ` Zac Medico
2009-09-19 22:52       ` [gentoo-dev] " Mark Bateman
2009-09-20 14:44     ` [gentoo-dev] " Jesús Guerrero
2009-09-20 15:46       ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 15:56         ` Nirbheek Chauhan
2009-09-20 16:07           ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 17:25             ` Nirbheek Chauhan
2009-09-20 17:35               ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 17:47                 ` Nirbheek Chauhan
2009-09-20 18:27                   ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 18:46                     ` Nirbheek Chauhan
2009-09-20 19:05                       ` Arfrever Frehtes Taifersar Arahesis
2009-10-08 20:56                       ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 16:51         ` Robert Buchholz
2009-09-20 17:25           ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 22:20             ` Mark Loeser
2009-09-21  1:17               ` Brian Harring
2009-09-21  6:18                 ` [gentoo-dev] " Duncan
2009-09-20 17:10         ` [gentoo-dev] " Petteri Räty
2009-09-19 18:22 ` Tobias Klausmann
2009-09-19 18:51   ` Arfrever Frehtes Taifersar Arahesis
2009-09-20 14:44     ` Jesús Guerrero
2009-09-19 18:45 ` Nirbheek Chauhan
2009-09-19 18:53   ` Arfrever Frehtes Taifersar Arahesis
2009-09-19 19:40     ` Nirbheek Chauhan
2009-09-19 19:35 ` Mark Loeser
2009-09-19 20:47   ` [gentoo-dev] " Ryan Hill
2009-09-19 20:55 ` [gentoo-dev] " Alistair Bush
2009-09-19 23:31   ` [gentoo-dev] " Ryan Hill
2009-09-19 23:45     ` Francesco R
2009-09-20  0:42       ` Alistair Bush
2009-09-20 14:46         ` Francesco R
2009-09-20 14:49   ` [gentoo-dev] " Jesús Guerrero

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=200909201725.00070.Arfrever@gentoo.org \
    --to=arfrever@gentoo.org \
    --cc=gentoo-dev@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