This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Daniel Colascione
Recipients Daniel Colascione, amaury.forgeotdarc, belopolsky, davin, meador.inge, pitrou, rhettinger
Date 2017-10-01.18:04:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKOZuev0xgNHPVhCsNMFD1fHG3r3qNNcdaNBadMex1mUGMdYWA@mail.gmail.com>
In-reply-to <1506879959.94.0.213398074469.issue31654@psf.upfronthosting.co.za>
Content
On Oct 1, 2017 10:46 AM, "Antoine Pitrou" <report@bugs.python.org> wrote:

Antoine Pitrou <pitrou@free.fr> added the comment:

While the use case is reasonable (if specialized),

It's not that specialized. You might want atomic updates for coordinating
with C APIs that expect callers to have this capability.

not sure ctypes is the place to expose such functionality, which can be
quite extensive (see https://gcc.gnu.org/onlinedocs/gcc/_005f_
005fatomic-Builtins.html).

You don't need to provide all of those builtins. Users can build them in
Python out of atomic-compare-and-exchange. Only compare and exchange needs
C support. It's not very much code.

Perhaps

as a separate package on PyPI?

I have little interest in a separate PyPI module. I don't want to have to
distribute custom-compiled extension modules.

----------

_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue31654>
_______________________________________
History
Date User Action Args
2017-10-01 18:04:41Daniel Colascionesetrecipients: + Daniel Colascione, rhettinger, amaury.forgeotdarc, belopolsky, pitrou, meador.inge, davin
2017-10-01 18:04:41Daniel Colascionelinkissue31654 messages
2017-10-01 18:04:41Daniel Colascionecreate