Martin v. Löwis wrote: > - PyGetSetDef (name, get, set, doc, closure) Is it fully decided that the generally-unused closure parameter will stay until python 4? > The accessor macros to these fields (Py_REFCNT, Py_TYPE, Py_SIZE) > are also available to applications. There have been several experiments in memory management, ranging from not bothering to change the refcount on permanent objects like None, to proxying objects across multiple threads or processes. I also believe (but don't remember for sure) that some of the proposed Unicode (or String?) optimizations changed the memory layout a bit. So far, these have all been complicated (or slow) enough that they didn't get integrated, but if it ever happens ... I don't think it would justify python 4.0 > New Python > versions may introduce new slot ids, but slot ids will never be > recycled. Slots may get deprecated, but continue to be supported > throughout Python 3.x. Weren't there already a few ready for deprecation? Do you really want to commit to them forever? Even if you aren't willing to settle for less than "3.x from now on", it might make sense to at least start with 3.2, rather than 3.0. -jJ
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