Message 217838 - Python tracker

➜

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	vstinner
Recipients	josh.r, jtaylor, neologix, njs, pitrou, python-dev, skrah, vstinner
Date	2014-05-03.22:49:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAMpsgwZrf=2EpevEFFJfTNBgVBiqx7r6Ok3HpzU8PK=Sz-niCw@mail.gmail.com>
In-reply-to	<1399154238.42.0.602663329801.issue21233@psf.upfronthosting.co.za>

Content
> 6) We need some kind of prominent documentation that existing > programs need to be changed: 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? 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.

> 6) We need some kind of prominent documentation that existing
>    programs need to be changed:

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?

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.

History
Date	User	Action	Args
2014-05-03 22:49:18	vstinner	set	recipients: + vstinner, pitrou, njs, skrah, neologix, python-dev, jtaylor, josh.r
2014-05-03 22:49:18	vstinner	link	issue21233 messages
2014-05-03 22:49:18	vstinner	create