Issue 22961: ctypes.WinError & OSError (original) (raw)

Issue22961

Created on 2014-11-28 06:37 by simonzack, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (4)
msg231796 - (view)	Author: Simon Zack (simonzack)	Date: 2014-11-28 06:37
The ctypes.WinError function returns: OSError(None, descr, None, code) However OSError does not appear to allow None as a first argument, and converts it to 22 which is the EINVAL "Invalid Argument" error. This is rather confusing as there was no invalid argument errors in the code. I think the behaviour for one of WinError and OSError should be modified so that the handling of errno is more compatible.
msg231805 - (view)	Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) *	Date: 2014-11-28 11:06
No, OSError.errno is converted from the Windows error code. There is a translation map (see PC/errmap.h, built with the _dosmaperr() function) and the default value is EINVAL. It's working as intended. What was the winerror code? do you think it should be mapped to another errno?
msg231806 - (view)	Author: Simon Zack (simonzack)	Date: 2014-11-28 11:28
Ok, my bad, I was creating my own OSErrors so I was just testing it out. I just found the default to be rather confusing as I thought None would not be mapped to anything.
msg231823 - (view)	Author: Eryk Sun (eryksun) *	Date: 2014-11-28 19:10
> the default value is EINVAL. Should that be specified in the docs? Currently it states that "[t]he errno attribute is then an approximate translation, in POSIX terms, of that native error code". https://docs.python.org/3/library/exceptions.html#OSError