From: "Dmitry S. Makovey" <dimon@makovey.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
Date: Mon, 13 Jun 2011 23:43:14 -0600 [thread overview]
Message-ID: <4DF6F4F2.5050704@makovey.net> (raw)
Hi everybody,
Is it me missing out on something or does KDE4 (namely PyKDE4) is borked
when default python is set to 3.1?
# eselect python list
Available Python interpreters:
[1] python2.7
[2] python3.1 *
# eselect python list --python3
Available Python 3 interpreters:
[1] python3.1 *
# eselect python list --python2
Available Python 2 interpreters:
[1] python2.7 *
# grep python /etc/make.conf
pygrub python python3 pulseaudio qalculate qt3 qt3support
with all of the above PyKDE4 compiles, however
kde-base/system-config-printer-kde-4.6.3 barfs:
Traceback (most recent call last):
File "/usr/share/apps/cmake/modules/FindPyKDE4.py", line 8, in <module>
import PyKDE4.pykdeconfig
with a bit of look-around it seems like pykde4 has:
RESTRICT_PYTHON_ABIS="2.4"
which boils down to (what seems like) pykde4 is built only for 3.1
# epm -ql pykde4 | grep pykdeconfig
/usr/lib64/python3.1/site-packages/PyKDE4/pykdeconfig.py
should I be performing some other waving in the air to make this whole
thing fly? It seems like a bug to me, but I'd rather confirm I'm not
missing something before reporting it.
next reply other threads:[~2011-06-14 5:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:43 Dmitry S. Makovey [this message]
2011-06-14 6:09 ` [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ? Mick
2011-06-15 0:09 ` Dmitry Makovey
2011-06-15 5:21 ` [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde? Mick
-- strict thread matches above, loose matches on Subject: below --
2011-06-14 17:38 [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ? Ulrich Drolshagen
2011-06-15 23:59 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF6F4F2.5050704@makovey.net \
--to=dimon@makovey.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox