View previous topic :: View next topic |
Author |
Message |
sgao Tux's lil' helper
Joined: 22 Apr 2006 Posts: 149
|
Posted: Thu Dec 27, 2012 10:11 pm Post subject: Why latest stage3 only has Python 3.2? Why??? |
|
|
Pulling down the latest minimal installation iso and stage3 package to install a new box. By a big surprise, I found only Python 3.2 was included in the stage 3 image.
This has caused endless problems to my installation. Never saw such messy installation process before. Bump into segfault, internal error almost at every turn. libxml2, pyqt4, pykde4, you named. Python 3.2 is not compatible with many KDE 4 packages. Why the hell dropping Python 2.x and only including Python 3.x before Python 3.x works with all packages? Even switching back to Python 2.7 and set only uses 2.7, things still fail here and there.
Anyone else experienced this mess? |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Thu Dec 27, 2012 11:15 pm Post subject: |
|
|
Well, no, but, after installing any new version of Python, you should run python-updater. Did you do that?
That's app-admin/python-updater, if you haven't already installed it.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
smartass Apprentice
Joined: 04 Jul 2011 Posts: 189 Location: right behind you ... (you did turn around, didn't you?)
|
Posted: Fri Dec 28, 2012 10:58 am Post subject: |
|
|
That sounds strange, PYTHON_TARGETS use expand should take care of that IIRC and pull in 2.7.
Do what John suggested, that could help, although it would be strange on a fresh stage3.
Just a few days ago I downloaded and installed stage3-amd64-20121210.tar.bz2 without any trouble,
and python2 got pulled in by some package, no trouble since. |
|
Back to top |
|
|
sgao Tux's lil' helper
Joined: 22 Apr 2006 Posts: 149
|
Posted: Sat Dec 29, 2012 4:57 pm Post subject: |
|
|
Python 2.7 is pulled in when installing some package that depends on Python 2.x.
Tried python-updater. It failed rebuilding boost.
How stable Python 3.2 is? |
|
Back to top |
|
|
smartass Apprentice
Joined: 04 Jul 2011 Posts: 189 Location: right behind you ... (you did turn around, didn't you?)
|
Posted: Sat Dec 29, 2012 7:26 pm Post subject: |
|
|
python 3.2 is considered production quality, just some libs haven't been ported to 3 yet.
But giving up and accepting 3 as the only solution to your problem is not a good idea IMHO, because you could have something much uglier going on in your system, the fact that boost wouldn't compile is a warning signal.
I suggest this if you haven't tried yet:
- check the control sum of the stage you downloaded and unpacked if you haven't deleted it yet ... chances (though thin) are you have a damaged stage
- try revdep-rebuild, emerge -NDu world, emerge -e system (remeber to use -a or -p and check the output before actually running the merge)... maybe your buildsystem is inconsistent
It's hard to tell what exactly is the problem in your case at this moment, but it's starting to sound like something beyond just python. |
|
Back to top |
|
|
|