Alec Warner wrote:
On Fri, Mar 26, 2010 at 4:08 PM, Dale<rdalek1...@gmail.com> wrote:
Arfrever Frehtes Taifersar Arahesis wrote:
2010-03-26 16:40:37 Brian Harring napisał(a):
There really isn't a precedent since upgrades of this sort typically
either have extremely locked down deps, or just plain don't happen
till the vast majority of depndencies are updated. If in doubt, look
at the past python upgrades- they've been delayed till all of the
major consumers played nice w/ the targeted python version.
Main active version of Python was automatically updated during previous
Python
upgrades, but it's not updated during installation of Python 3.1.
As a user, I still think this could turn into a real mess. I think there
will be quite a few that will see python being updated, run python-updater
and switch it to the new python. At that point, it is going to hit the fan.
I know because this is what I always do. News item or not, when python
gets updated, I run python-updater and make sure it is selected.
My assumption here is that eselect-python will not let you select v3
as your python version without some prodding (eg setting stupid
environment variables or similar.)
r...@smoker ~ # eselect python list
Available Python interpreters:
[1] python2.6 *
[2] python3.1
r...@smoker ~ # eselect python set 2
r...@smoker ~ # eselect python list
Available Python interpreters:
[1] python2.6
[2] python3.1 *
r...@smoker ~ #
That was pretty easy to select the new python. Everything I did was
right there. Two commands and it is switched. This is where problems
will start.
If this somehow breaks portage, which it shouldn't since apparently portage
is fine with the new python, then it is going to really hit the fan.
Me, I'm going to make SURE nothing changes on my system. Then I'm going to
sit back and see what happens, good or bad. I can't imagine anything good
but I sure can imagine bad things.
Such faith ;)
Dale
:-) :-)
It's not faith, its reality. There will be some people that don't
subscribe to this list that will do what is above. This IS the reason I
subscribed to this list. I wanted to know what the devs were doing
under the hood that would lead me to screw up my system. It's amazing
how much fewer problems I have had since I started watching this list.
Also, if python3 is marked as "stable," people will assume it is safe to
switch to. That's what "stable" means.
Back to my hole.
Dale
:-) :-)
