Brett Cannon added the comment:
Should we just close this, Barry?
--
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13572
___
STINNER Victor added the comment:
The issue obviously in PyUnicode_FromString() call from
PyCursesWindow_GetKey().
We can try latin1 encoding, locale encoding or utf-8 with surrogateescape
error handler.
PyUnicode_FromString() uses the UTF-8 decoder. I don't think that curses uses
any
Changes by Serhiy Storchaka storch...@gmail.com:
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13572
___
___
Serhiy Storchaka added the comment:
Barry, you can reproduce it? The issue obviously in PyUnicode_FromString() call
from PyCursesWindow_GetKey(). We can try latin1 encoding, locale encoding or
utf-8 with surrogateescape error handler.
--
nosy: +serhiy.storchaka
status: pending - open
Serhiy Storchaka added the comment:
Here are three patches. I think one of them (or any) should fix the issue. The
question is what solution returns more suitable result for non-ascii key
names.
--
keywords: +patch
Added file:
Barry A. Warsaw added the comment:
I cannot reproduce it with Python 3.3 hg head on my ARM buildbot. _curses
builds and imports just fine now.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13572
STINNER Victor added the comment:
What is the status of this issue? Is anyone able to reproduce it? If not, I
would like to close it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13572
Brett Cannon added the comment:
I can't, so setting to pending so that if no one speaks up the issue will close.
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13572
Brett Cannon br...@python.org added the comment:
This fails for me on OS X Snow Leopard using LLVM 3.0.
And I agree with your initial guess, Victor: I don't see how importlib could
possibly be the issue here since it's using load_dynamic() and not loading some
Python source itself.
STINNER Victor victor.stin...@haypocalc.com added the comment:
@Barry: can you try to get a trace using gdb? Start python in gdb, set a
breapoint on PyErr_SetObject, continue, run the Python command import
_curses, get the gdb traceback (or continue if the error is not the UTF-8
error).
New submission from STINNER Victor victor.stin...@haypocalc.com:
http://www.python.org/dev/buildbot/all/builders/ARM%20Ubuntu%203.x/builds/143/steps/test/logs/stdio
---
test test_curses crashed -- Traceback (most recent call last):
File
STINNER Victor victor.stin...@haypocalc.com added the comment:
The compilation of the module failed for the same reason:
building '_curses' extension
gcc -pthread -fPIC -Wno-unused-result -g -O0 -Wall -Wstrict-prototypes
-DHAVE_NCURSESW=1 -I/usr/include/ncursesw -IInclude -I. -I./Include
STINNER Victor victor.stin...@haypocalc.com added the comment:
The problem comes maybe from the name of a curses key, keyname().
PyInit__curses() gets the name of all keys (KEY_MIN..KEY_MAX).
--
___
Python tracker rep...@bugs.python.org
Barry A. Warsaw ba...@python.org added the comment:
Fails in exactly the same way when built from my shell account using current hg
head. Does not fail on same version of OS on amd64.
--
___
Python tracker rep...@bugs.python.org
14 matches
Mail list logo