On Fri, Mar 5, 2010 at 10:41, Joshua Saddler <nightmo...@gentoo.org> wrote: >>> 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?
Because it's a frigging major revision that breaks some backwards compatibility! >>> 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. I don't want to force stable users to install it. I *do* however want to install it as part of the stable tree on some of my servers. And I don't think it's sensible that I have to force it to be stable somehow, I want my packagers to say, hey, we checked this and it should just work (for the intended purpose, which is NOT running code written for python2). > 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. I agree that that's bad, but I do not agree that not stabilizing it is the right solution. > No one has said yet why this is. So . . . direct question, gimme a direct > answer: why? Because in my opinion stable means that the people who package this are stating that hey, we did some testing with this, it works with all of the other packages you have installed that want to use it. It does not mean everyone should have it installed, which is what it appears you think it means. Cheers, Dirkjan
