Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2021 12:54:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 245773] lang/python3: Missing errno.EDEADLOCK
Message-ID:  <bug-245773-21822-xJXUHaKrUT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-245773-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-245773-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245773

--- Comment #3 from Gleb Popov <arrowd@FreeBSD.org> ---
(In reply to Willem Jan Withagen from comment #2)

> But it would be a lot more conveinient if it did exist and worked as expe=
cted.

And what's expected in this case? I, for example, expect an undefined const=
ant,
because FreeBSD doesn't have EDEADLOCK code.

> Then again Python claims that it errno.EDEADLOCK is there,

Actually, at the top of https://docs.python.org/3/library/errno.html there =
is a
following sentence:

> Of the following list, symbols that are not used on the current platform =
are not defined by the module. The specific list of defined symbols is avai=
lable as errno.errorcode.keys().

I think there is no bug here. At least, no FreeBSD-specific one. If the
reporter believes that EDEADLOCK should be automatically mapped to somethin=
g,
the right thing is to open a PR on the Python bug tracker.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245773-21822-xJXUHaKrUT>