Alan McKinnon wrote:
Agreed. The elog message strikes me as merely an enthusiastic endorsement of
cool shiny new stuff from an over-zealous maintainer who doesn't quite grasp
how slow traction can be in the real world
While that may be true, and even though he did make a few mistakes in
the
On Tue, 08 Dec 2009 09:02:47 +0100, Remy Blank wrote:
So, going back to the initial question, you could just emerge Python
3.1, enable it in USE_PYTHON in make.conf, but leave 2.6 as a default.
Where is USE_PYTHON documented? I see no mention of it in man make.conf,
make.conf.example or the
Neil Bothwick wrote:
Where is USE_PYTHON documented? I see no mention of it in man make.conf,
make.conf.example or the portage elogs.
In /usr/portage/eclass/python.eclass ;-)
To be honest, I wanted that feature so badly that I dug through
python.eclass as soon as I saw arfrever mention it.
On 2009-12-07, Alan McKinnon alan.mckin...@gmail.com wrote:
On Monday 07 December 2009 22:24:14 Grant Edwards wrote:
My most recent update displayed the following messages from
Python 2.6.4 and Python 2.4.6:
It is highly recommended to additionally install Python 3,
Why is it highly
On Tuesday 08 December 2009 00:41:57 Grant Edwards wrote:
Quoting from the page on Python 2.7 (released today):
Python 2.7 is scheduled to be the last major version in the
2.x series before it moves into 5 years of bugfix-only mode.
So there's at least 5 years of life left in the 2.x
5 matches
Mail list logo
