Philip Semanchuk added the comment:
> On Feb 23, 2019, at 10:40 AM, Giampaolo Rodola'
> wrote:
>
>
> Giampaolo Rodola' added the comment:
>
>> We are consciously choosing to not support an atomic "create or attach".
>> This significantly simplifi
Philip Semanchuk added the comment:
Hi all, I'm the author of `posix_ipc` on which some of this code is based. I'd
be happy to sign a contributor agreement in order to erase any concerns on that
front.
--
nosy: +osvenskan
___
Python tracker
Changes by Philip Semanchuk osvens...@users.sourceforge.net:
--
nosy: +osvenskan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20584
Changes by Philip Semanchuk osvens...@users.sourceforge.net:
--
nosy: +osvenskan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8426
___
___
Python
Philip Semanchuk osvens...@users.sourceforge.net added the comment:
I stumbled across this bug report while looking for an mmap-related
issue. I thought I'd mention that I have a module for SysV IPC that's
about a year old.
Obviously it's not in the standard library, but it is pretty well
New submission from Philip Semanchuk osvens...@users.sourceforge.net:
The language in the threading API documentation is a little
inconsistent. The section I'm talking about is here:
http://docs.python.org/c-api/init.html#thread-state-and-the-global-interpreter-lock
The GIL is variously
New submission from Philip Semanchuk osvens...@users.sourceforge.net:
The threading API documentation might omit out some important
information about the GIL.
The GIL can be acquired by explicitly calling PyEval_AcquireLock(). One
can also acquire the GIL by calling PyGILState_Ensure
