RetroSearch Browse

Sun Jan 8 09:42:48 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-January/115404.html

On 08/01/12 19:07, Paul Smedley wrote:
> On 07/01/12 08:22, Paul Smedley wrote:
>>> For the purpose of debugging you could *not* ignore the error and
>>> instead print it out or bail out.
>> Thanks - commenting out the ImportErrors block, I get:
>> ImportError: No module named encodings
>
> OK got through this - PYTHONPATH in makefile was borked for OS/2 (:
> separators vs ; which don't work so well with drive letters)
>
> Now having trouble importing the _io module even though it's builtin <sigh>
>
to be clear, the error is:
Fatal Python error: Py_Initialize: can't initialize sys standard streams
Traceback (most recent call last):
   File "U:/DEV/python-3.2.2/Lib/io.py", line 60, in <module>

Killed by SIGABRT

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-January/115404.html below:

[Python-Dev] What's required to keep OS/2 support in Python 3.3