A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2019-February/156381.html below:

[Python-Dev] Making PyInterpreterState an opaque type

[Python-Dev] Making PyInterpreterState an opaque type [Python-Dev] Making PyInterpreterState an opaque typeNick Coghlan ncoghlan at gmail.com
Tue Feb 19 09:00:16 EST 2019
On Tue, 19 Feb 2019 at 20:41, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Mon, 18 Feb 2019 19:04:31 -0800
> Steve Dower <steve.dower at python.org> wrote:
> > If you always rebuild your extension for every micro version (3.x.y) of
> > CPython, then sure, go ahead and use this.
>
> Usually we would guarantee that API details don't change in bugfix
> versions (i.e. the 3.x.y -> 3.x.(y + 1) transition).  Has that changed?
> That may turn out a big problem for several third-party extensions...

This is the genuine technical difference between the three levels:

* Py_BUILD_CORE -> no ABI stability guarantees at all
* standard -> stable within a maintenance branch
* Py_LIMITED_API -> stable across feature releases

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4