Ned Deily added the comment:
Usually this kind of problem is caused by not having the necessary developer
package of ncurses installed when building Python. The dev package includes
the header files necessary for Python's curses module to build and link with
libncurse{,w}. When you build Python 3.3.1, there probably was a message like:
Python build finished, but the necessary bits to build these modules were not
found:
_curses
I'm not familiar with Linux Mint but, if it is Debian or Ubuntu-based, try
installing the libncurses5-dev package and rebuilding Python. The 3.3 _curses
modules you show in /usr/lib are most likely left over from a previous Python
3.3.0 installation, possibly from a Linux Mint package. Note that the _curses
files are installed in /usr/lib/python3.3 whereas the traceback from your
Python 3.3.1 shows a /usr/local/lib/python3.3 path which is the default
location if you built and installed it yourself. When built and installed,
_curses should end up in /usr/local/lib/python3.3/lib-dynload.
----------
nosy: +ned.deily
resolution: -> invalid
stage: -> committed/rejected
status: open -> pending
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17704>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
