Console commands and Python 3.2 [Case closed]

[jake_mcaga]

Dunno if this is really a PCLOS-bug or not. I've downloaded and compiled python 3.2 for both my laptops. It works fine on the Compaq with Luscious Lamb Chops 9.10 Gnome, but on this one (DELL Vostro 1000) with PCLOS KDE 2010.12 (and yeah, just upgraded the system with Synaptic) ctrl+L, cursor keys etc. (all those things that work in the console and yakuake) won't work inside the python 3.2 interpreter.
(The usual Python 2.x works fine by the way on this laptop)
Does anyone know why? And how to fix it?

Thanks.

[jake_mcaga]

Add-on:

Just got a reply from python.org. They say this isn't Python's fault. Citation:

"I believe this is out of scope for Python itself, and is a platform distribution issue.  The platform must do some special magic to make those things work; they don't in a vanilla python build as far as I know.  You might look to your readline configuration for clues."

So I'm still in the dark. Can anyone help?

Thanks.

[Neal ManBear]

It looks like you are being told that you need to check how you configured the install.

.....look to your readline configuration....

If you replaced the default install of python (2.6) with 3.2, you'll need to check /usr/bin/python-config and edit it as needed. If you did not replace the default, you will need to edit the config file for 3.2.
Replacing the default install of python is not a good idea, as those applications that are dependent on it will not work or not work properly.

[jake_mcaga]

Hi.

Thanks for the reply, and sorry for being away too long. I'm a newb and compiling python3 for my system was my first try at the configure-make-make install process of any program at all. (I used the alt-install alternative. Python3.2 works nicely by itself, side by side 2.6 although Bash short-cuts aren't interpreted in 3.2 ).
I think this is beyond me as I'm just starting out. I'm inclined to wait until PCLOS creates packages (for Python3.x) to install. Editing the config file for 3.2? There are several files. Skimmed through them all, although I understand bits of them, I don't even know what to look for. Yes, there are errors, but they're way beyond my understanding. Some are in C header files.

So, case closed (until further notice).
(I can remove this topic, if desirable)

[Neal ManBear]

Naw. Just leave it here.

[Texstar]

Python 3 is in the special section but you need to read up on how to enable it for your purposes.