| 1 |
On Fri, Mar 5, 2010 at 10:41, Joshua Saddler <nightmorph@g.o> wrote: |
| 2 |
>>> Python 3 is a new major version of Python and is intentionally incompatible |
| 3 |
>>> with Python 2. Many external modules have not been ported yet to Python 3, so |
| 4 |
>>> currently Python 3.1 should not be set as main active version of Python. |
| 5 |
>>> Setting Python 3.1 as main active version of Python is currently unsupported. |
| 6 |
>>> When it will change, a separate news item will be created to notify users. |
| 7 |
> |
| 8 |
>>So nothing uses it yet, and it's completely incompatible with 90% of the |
| 9 |
>>numerous python/pygtk apps already on my system, so it'll just sit there, |
| 10 |
>>SLOTted, doing nothing but taking up more space on my very limited SSD, while |
| 11 |
>>Python 2.6 is the version that's actually in use by every single app. |
| 12 |
> |
| 13 |
> 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? |
| 14 |
|
| 15 |
Because it's a frigging major revision that breaks some backwards compatibility! |
| 16 |
|
| 17 |
>>> Currently Python 3.1 should *NOT* be set as [the] main active version of |
| 18 |
>>> Python. |
| 19 |
> |
| 20 |
> This is in the friggin' news item itself. If it should not be used, then don't force stable users to install it. |
| 21 |
|
| 22 |
I don't want to force stable users to install it. I *do* however want |
| 23 |
to install it as part of the stable tree on some of my servers. And I |
| 24 |
don't think it's sensible that I have to force it to be stable |
| 25 |
somehow, I want my packagers to say, hey, we checked this and it |
| 26 |
should just work (for the intended purpose, which is NOT running code |
| 27 |
written for python2). |
| 28 |
|
| 29 |
> 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. |
| 30 |
|
| 31 |
I agree that that's bad, but I do not agree that not stabilizing it is |
| 32 |
the right solution. |
| 33 |
|
| 34 |
> No one has said yet why this is. So . . . direct question, gimme a direct answer: why? |
| 35 |
|
| 36 |
Because in my opinion stable means that the people who package this |
| 37 |
are stating that hey, we did some testing with this, it works with all |
| 38 |
of the other packages you have installed that want to use it. It does |
| 39 |
not mean everyone should have it installed, which is what it appears |
| 40 |
you think it means. |
| 41 |
|
| 42 |
Cheers, |
| 43 |
|
| 44 |
Dirkjan |
Archives