On 03/07/2010 07:11 PM, Mark Loeser wrote:
> Sebastian Pipping <sping@g.o> said:
>> On 03/04/10 19:22, Arfrever Frehtes Taifersar Arahesis wrote:
>>> All problems, which were blocking stabilization of Python 3, have been fixed.
>>> Stabilization of Python 3.1.2 is currently scheduled on 2010-04-19.
>>
>> #python on Freenode still reads "It's too early to use Python 3.x".
>> Are they wrong?
> 
> I'd believe them.
> 
>> Are we at a point already where we can feed 90% of the Python 2.x code
>> out there to Python 3 without problems?
> 
> Doesn't seem that way.
> 
>> Has QA given their blessing to this?
> 
> Absolutely not.  Its actually the opposite.  Until 90+% of the tree just
> works with the new version of python, it should not be stabilized.  The
> stable tree should all Just Work together.  Stabilizing python-3 at this
> point would be the equivalent of me stabilizing gcc-4.5 after its been
> in the tree for a few months and nothing else works with it.  Sure, gcc
> works just fine, but it can't compile half of the tree.
> 
> I hope everyone can see that this is a terrible idea and of no use to
> our stable users.  If a stable user really needs Python-3, they will
> have the technical ability to unmask it and use it properly.
> 

+1

no need to stabilize experimental python, not even convinced it should
be in ~arch yet (but package.masked for testing)