Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
On Tue, Jun 14, 2011 at 07:38:56PM +0200, Ulrich Drolshagen wrote I'm not Dmitry but I am using 3.1 too. 3.1 is set as default by stage1 for some time now. No issues with 3.1 here though, at least none that are related to python. Why do they set it default by stage1 and warn not to use it at the same time? Gentoo does not use that type of install anymore for standard installs. Stage 1 is for experimentation and developers only, not for regular users. The rules that apply to stage 1 do not apply to ordinary installs. See http://www.gentoo.org/doc/en/faq.xml#stage12 How do I Install Gentoo Using a Stage1 or Stage2 Tarball? The Gentoo Handbook only describes a Gentoo installation using a stage3 tarball. However, Gentoo still provides stage1 and stage2 tarballs. This is for development purposes (the Release Engineering team starts from a stage1 tarball to obtain a stage3) but shouldn't be used by users: a stage3 tarball can very well be used to bootstrap the system. You do need a working Internet connection. -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
On Tuesday 14 Jun 2011 06:43:14 Dmitry S. Makovey wrote: 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. The last enews I read specifically warned *not* to turn on 3.1 and instead stay with the latest 2 version ... Do you have a specific reason that compels you to try to make KDE work with 3.1? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
Am Dienstag, 14. Juni 2011, 08:09:57 schrieb Mick: 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. The last enews I read specifically warned *not* to turn on 3.1 and instead stay with the latest 2 version ... Do you have a specific reason that compels you to try to make KDE work with 3.1? I'm not Dmitry but I am using 3.1 too. 3.1 is set as default by stage1 for some time now. No issues with 3.1 here though, at least none that are related to python. Why do they set it default by stage1 and warn not to use it at the same time? Regards, Ulrich -- http://www.ulrich-drolshagen.de
Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
On 06/14/2011 12:09 AM, Mick wrote: The last enews I read specifically warned *not* to turn on 3.1 and instead stay with the latest 2 version ... Do you have a specific reason that compels you to try to make KDE work with 3.1? If memory serves me right it was on this list that I picked up the idea that things are working just fine with 3.1, not to mention that most packages are smart enough to know which python they need with PYTHON_API variables sprinkled around ebuilds. So I was quite surprised to uncover this one.
Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde?
On Wednesday 15 Jun 2011 01:09:28 Dmitry Makovey wrote: On 06/14/2011 12:09 AM, Mick wrote: The last enews I read specifically warned *not* to turn on 3.1 and instead stay with the latest 2 version ... Do you have a specific reason that compels you to try to make KDE work with 3.1? If memory serves me right it was on this list that I picked up the idea that things are working just fine with 3.1, not to mention that most packages are smart enough to know which python they need with PYTHON_API variables sprinkled around ebuilds. So I was quite surprised to uncover this one. Indeed package deps should take advantage of python3 as long as it has been installed, if the package needs python3: === # eselect news read 3 2010-03-25-python-3.1 Title Python 3.1 AuthorArfrever Frehtes Taifersar Arahesis arfre...@gentoo.org Posted2010-03-25 Revision 1 Python 3 is a new major version of Python and is intentionally incompatible with Python 2. Many external modules have not been ported yet to Python 3, so Python 2 still needs to be installed. You can benefit from having Python 3 installed without setting Python 3.1 as main active version of Python. Currently you should not set Python 3.1 as main active version of Python. When setting it becomes recommended, a separate news item will be created to notify users. Although Python 3.1 should not be set as main active version of Python, you should run python-updater after installation of Python 3.1. By default, modules that support both Python 2 and Python 3 are installed for both the active version of Python 2 and the active version of Python 3 when both Python 2 and Python 3 are installed. It is recommended to use a UTF-8 locale to avoid potential problems. Especially C and POSIX locales are discouraged. If locale has not been explicitly set, then POSIX locale is used, so you should ensure that locale has been set. Problems occurring only with non-UTF-8 locales should be reported directly to upstream developers of given packages. See http://www.gentoo.org/doc/en/utf-8.xml for more information about UTF-8. === This news item and the elog messages/warnings make me think that python3 time has not come yet. YMMV -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
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.
