Neil Schemenauer <nas@python.ca> writes: > > No, it's for the binary API. There's a test in Py_InitModule() that > > checks whether a dynamically loaded extension uses the same API as the > > core, and that's definitely a binary compatibility issue. > > I was under the impression that the binary API changes in every minor > release. (By minor, you mean the y in x.y.z?) On Windows, yes - the DLL name changes, causing problems for old extensions. On Unix, not necessarily - atleast not in incompatible ways. I think the API didn't change between 1.6 and 2.0 (see Include/modsupport.h); I'm not sure whether 2.3 will see an API change. Regards, Martin
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