Re: [gentoo-dev] Python 3.1: Stabilization and news item

[Joshua Saddler <nightmorph@gentoo.org>]

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

On Fri, 5 Mar 2010 10:10:00 +0100
Dirkjan Ochtman <djc@gentoo.org> wrote:

> Because 'stable' denotes that it works as intended, that it can be
> installed easily, etc. All of these are true now for python3. There
> are applications being written for it. We want to package those too.
> I'm fine with people masking it, and maybe we should make that easier
> somehow, but 3.x should definitely be stable.

It does *not* work as intended.

Here, since your selective quoting missed every point I made, lemme make 'em again:

>> Python 3 is a new major version of Python and is intentionally incompatible
>> with Python 2. Many external modules have not been ported yet to Python 3, so
>> currently Python 3.1 should not be set as main active version of Python.
>> Setting Python 3.1 as main active version of Python is currently unsupported.
>> When it will change, a separate news item will be created to notify users.  

>So nothing uses it yet, and it's completely incompatible with 90% of the
>numerous python/pygtk apps already on my system, so it'll just sit there,
>SLOTted, doing nothing but taking up more space on my very limited SSD, while
>Python 2.6 is the version that's actually in use by every single app.

Like I said before, like it says *in the news item*, "stuff does not work with it." How does that qualify as "works as intended" when it will not work with all my packages that use Python?

If you believe stabilizing a package should be done in a vacuum, in an idealized world where no other package cares about another, then congrats, you're on the right track.

>> Currently Python 3.1 should *NOT* be set as [the] main active version of
>> Python.

This is in the friggin' news item itself. If it should not be used, then don't force stable users to install it.

> It will *NOT* under this proposal be the default. Please formulate
> more carefully if you want to make an argument.

If it's stable, then users get it by default, assuming they run the stable tree. They install a recent stage3, build their system, run emerge -uD world. Bam, a useless version of Python is now installed. Nothing on their systems will use it, so it's bloat.

> but 3.x should definitely be stable

No one has said yet why this is. So . . . direct question, gimme a direct answer: why?

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