Jason R. Coombs <jaraco@jaraco.com> added the comment:
I've confirmed that my original assumption was quite false, and that
even if the parameters are the correct width, WNetAddConnection2W
behaves differently in 64-bit windows versus 32-bit windows, so it made
a bad test case.
So I've changed the title of this issue, because I still would like to
know if it is proper for ctypes to accept a narrow string but treat it
as a wide string without converting it.
----------
title: inconsistent wide character parameter handling in 64-bit python -> wide character parameter handling in ctypes
_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue5119>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
I've confirmed that my original assumption was quite false, and that
even if the parameters are the correct width, WNetAddConnection2W
behaves differently in 64-bit windows versus 32-bit windows, so it made
a bad test case.
So I've changed the title of this issue, because I still would like to
know if it is proper for ctypes to accept a narrow string but treat it
as a wide string without converting it.
----------
title: inconsistent wide character parameter handling in 64-bit python -> wide character parameter handling in ctypes
_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue5119>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com