[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2015-07-29 Thread STINNER Victor
Changes by STINNER Victor : -- superseder: -> Remove unsupported code from ctypes ___ Python tracker ___ ___ Python-bugs-list mailing

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2015-07-29 Thread Steven Barker
Steven Barker added the comment: I was looking over some of the bugs I've contributed to, and it looks like this one has been fixed. It should be marked as a dupe of issue 22161 and closed (I can close, but not set a superseder, it seems). -- resolution: -> duplicate status: open -> c

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-06-04 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-06-02 Thread Shriramana Sharma
Shriramana Sharma added the comment: I came upon this too. In Python 2 it used to expect a one character string. Apparently the same error message has been carried forward to Python 3 too, though now the actual expected input is either a one character bytes type and not a str type, or an int c

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-05-17 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- nosy: +amaury.forgeotdarc, meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-05-15 Thread Steven Barker
Changes by Steven Barker : -- components: +ctypes -Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17991] ctypes.c_char gives a misleading error when passed a one-character unicode string

2013-05-15 Thread Steven Barker
New submission from Steven Barker: While investigating a Stack Overflow question (http://stackoverflow.com/questions/16484764/multiprocessing-value-clear-syntax) I came across a misleading error message from the multiprocessing.Value constructor: >>> import multiprocessing >>> my_char = "x" >