Author skrah
Recipients josh.r, jtaylor, neologix, njs, pitrou, python-dev, skrah, vstinner
Date 2014-05-04.11:12:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20140504111203.GA16483@sleipnir.bytereef.org>
In-reply-to <CAMpsgwZrf=2EpevEFFJfTNBgVBiqx7r6Ok3HpzU8PK=Sz-niCw@mail.gmail.com>
Content
STINNER Victor <report@bugs.python.org> wrote:
> My final commit includes an addition to What's New in Python 3.5 doc,
> including a notice in the porting section. It is not enough?

I'm not sure: The usual case with ABI changes is that extensions may segfault
if they are *not* recompiled [1].  In that case documenting it in What's New is
standard procedure.

Here the extension *is* recompiled and still segfaults.

> Even if the API is public, the PyMemAllocator thing is low level. It's not
> part of the stable ABI. Except failmalloc, I don't know any user. I don't
> expect a lot of complain and it's easy to port the code.

Perhaps it's worth asking on python-dev. Nathaniel's suggestion isn't bad
either (e.g. name it PyMemAllocatorEx).

[1] I was told on python-dev that many people in fact do not recompile.
History
Date User Action Args
2014-05-04 11:12:04skrahsetrecipients: + skrah, pitrou, vstinner, njs, neologix, python-dev, jtaylor, josh.r
2014-05-04 11:12:04skrahlinkissue21233 messages
2014-05-04 11:12:04skrahcreate