| View previous topic :: View next topic |
| Author |
Message |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
 Posted: Tue Oct 21, 2014 11:08 am Post subject: portage won't build for active python? |
 |
|
I keep seeing the following message after emerging packages:
| Code: | * Building package for python3.3 only while python3.4 is active.
* Please consider switching the active Python 3 interpreter:
*
* eselect python set --python3 python3.3
*
* Please note that after switching the active Python interpreter,
* you may need to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
|
If I read this correctly, python is set to 3.4, but portage won't build for that version, because it's … active? I have correctly used 'eselect python' to set python to 3.4 and used python-updater (which only updated bibtex and calibre anyway), and still see this message.
Am I missing something here, or is this some unintended/improperly-configured behavior on the part of portage? How do I build packages with support for the active python version?
Cheers,
EE |
|
| Back to top |
|
 |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Tue Oct 21, 2014 11:27 am Post subject: |
|
|
What is your output of | Quote: | | $ eselect python list |
The line with the asterisk behind is your active version. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Oct 21, 2014 11:28 am Post subject: |
|
|
| Code: | # eselect python list
Available Python interpreters:
[1] python2.7
[2] python3.2
[3] python3.3
[4] python3.4 *
|
Like I said: 3.4 is the active one, but a bunch of packages are apparently refusing to build for it, because it's, uh … active. Are there a lot of packages that aren't compatible with 3.4 still?
Cheers,
EE |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Tue Oct 21, 2014 11:38 am Post subject: |
|
|
Please check | Quote: | | $ eix -I -U python_single_target_python2.7 |
and check the same for 3_4
You might find lots of packages not yet ready for 3.4.
You'd better update from 3.2.5-r6 to 3.3.5-r1 and set active version to python3.3 |
|
| Back to top |
|
|
i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
| Posted: Tue Oct 21, 2014 11:50 am Post subject: |
|
|
I don't have direct experience with 3.4. But if I speak from my experience which goes back to 2.2 (or 2.1, can't remember...), it's a really bad idea to live on the edge when it comes to python. That is, unless you are intending to develop with that concrete version.
If it goes just like the last 14 years, then it will take a lot of time until it gets into decent shape. Note that, by now, you still need to have 2.7 around for a few packages. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
| Posted: Tue Oct 21, 2014 11:51 am Post subject: |
|
|
I do not, apparently, have eix installed. I'll let you know when I have it.
The "no module named 'portage'" thing I just, uh, ignored.
Setting PYTHON_TARGETS="3_4" in make.conf leads to a bunch of dependency conflicts, most notably in portage but also a few other packages. I guess I'll leave it unspecified and take this error message to mean that the package in question isn't ready for 3.4 yet?
Cheers,
EE |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Tue Oct 21, 2014 12:10 pm Post subject: |
|
|
| You'd better remove any PYTHON... stuff from /etc/portage/make.conf unless you have severe demand to have. |
|
| Back to top |
|
|
grumblebear
Apprentice
Joined: 26 Feb 2008
Posts: 202
|
| Posted: Tue Oct 21, 2014 12:29 pm Post subject: |
|
|
To get rid of Python-3.3 in favor of Python-3.4:
- Set PYTHON_TARGETS="python2_7 python3_4" in make.conf
- echo '-python_targets_python3_4' >> /etc/portage/profile/use.stable.mask
- echo 5 > /etc/portage/profile/eapi
Then emerge --update --newuse --deep --with-bdeps y world. And run python-updater.
I doubt there will be any problems switching from Python-3.3 to Python-3.4. Check Bugzilla if unsure. |
|
| Back to top |
|
|
|
Portage & Programming
