[ python-Bugs-823672 ] os.strerror doesn't understand windows error codes

[SourceForge.net]

Bugs item #823672, was opened at 2003-10-14 22:04
Message generated for change (Comment added) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=823672&group_id=5470

Category: None
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Thomas Heller (theller)
Assigned to: Nobody/Anonymous (nobody)
Summary: os.strerror doesn't understand windows error codes

Initial Comment:
For example, os.strerror(errno.EWOULDBLOCK) returns
'unknown error'.

----------------------------------------------------------------------

>Comment By: Jack Jansen (jackjansen)
Date: 2003-12-07 23:33

Message:
Logged In: YES 
user_id=45365

That depends: if the C library returns EWOULDBLOCK in errno and 
then refuses to understand it in strerror() this is indeed not 
Python's problem. But if the C library never set errno to 
EWOULDBLOCK  but we somehow generate it (and grepping on 
EWOULDBLOCK seems to indicate there could be something fishy 
going on with EWOULDBLOCK and WSAEWOULDBLOCK) we should 
have the courtesy to understand it in strerror().

I'll leave it to someone else to decide whether this makes sense 
and the bug should be reopened.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2003-10-24 22:15

Message:
Logged In: YES 
user_id=21627

Why is this a bug in Python? os.strerror just calls the
system's strerror(3). If that doesn't know its own errors,
how should Python know?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=823672&group_id=5470