On 12/4/22 13:08, Eryk Sun wrote:
On 12/2/22, biglee12...@gmail.com <biglee12...@gmail.com> wrote:
From this point on Python became unusable as I uninstalled rebooted then
reinstalled to find I have the same issues as stated. Finally uninstalled
Python as it doesn't perform as usual especially trying to understand the
use of pyreadline, gnureadline and or just readline.
When Python runs interactively, it implicitly tries to import the
readline module. On POSIX, Python has a builtin readline module that
usually uses the GNU Readline library.
On Windows, Python does not include a readline module. Instead, if
standard I/O is a console, the high-level WinAPI ReadConsoleW()
function is used, which implements its own line editor and
command-line history. It's not as general, flexible, or capable as the
readline interface, so a third-party pyreadline package was
implemented for Windows. However, as far as I know, pyreadline is no
longer actively developed. Thus it has out-of-date code, which may be
broken in newer releases of Python, such as isinstance(x,
collections.Callable).
Your choice is to either patch pyreadline to fix the bug or uninstall it.
there is a pyreadline3
I tried it for a particular case and didn't have a whole lot of luck
with it, so YMMV, but somebody has done the porting work to keep it more
current.
--
https://mail.python.org/mailman/listinfo/python-list
