New submission from Rocco Matano :
When using ctypes under Windows, I have observed a baffling behavior which I am
not sure if it is the result of a bug in ctypes, or is simply due to false
expectations on my part.
Environment:
- Windows 10 Pro, 21H1, 19043.1586, x64
- Python versions 3.6
Rocco Matano added the comment:
@Eryk I think you hit the nail on the head with your recommendation to avoid
ctypes.c_wchar_p (i.e. wintypes.LPWSTR) as the parameter type when dealing
resource type/name strings. Of course ctypes automatic conversion from a C
character pointer to a Python
Rocco Matano added the comment:
I forgot to say thank you. I would like to make up for that:
Thank you, Eryk.
--
___
Python tracker
<https://bugs.python.org/issue47
Rocco Matano added the comment:
I just experienced the described problem using Python 3.6.0 (Python 3.6.0
(v3.6.0:41df79263a11, Dec 23 2016, 08:06:12) [MSC v.1900 64 bit (AMD64)] on
win32), but i do not understand the current status of this issue: On the one
hand it is marked as 'open&#x
New submission from Rocco Matano:
On windows and python up to 3.4 using the combination of os.spawnX(os.P_NOWAIT,
...) and os.waitpid() worked as expected, but with python 3.5 this no longer
works. In fact os.waitpid() now raises an OSError when the child process
terminates.
Running this
Rocco Matano added the comment:
I know that using os.spawn and and os.waitpid this way is not the best option,
but a 3rd party tool i am using (scons) is doing it that way. So no scons with
Python 3.5.0. (I am also aware that scons does not yet support Python 3.x
officially
