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
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
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 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
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?
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
6 matches
Mail list logo
