* Change ABI management to encourage pre-built wheels
* Actually dedicate a subsection to the 2 year cadence
* Update naming discussion for proposal changes
* Add discussion section for the pre-freeze flag
* Make the abstract much shorter (as suggested by Antoine Pitrou)
* Move example time line up and add pictures (based on PEP 602 images)
* Clarify 4 month window for X.Y.0a1 preparation
Co-Authored-By: Steve Dower <steve.dower@microsoft.com>
* proposes the regular publication of production-ready beta releases rather than making full X.Y.0 feature releases more common
* PEP 598 is being withdrawn in favour of this proposal
* originally drafted in collaboration with @zooba, @aeros167, and @h-vetinari
Matching the symbols permitted for x86_64 by GCC_4.3.0 require a limit of GCC_4.5.0 on i686 CentOS 6.
This does create the risk that 32-bit extension modules using `__extendxftf2` may not actually be portable to all 2010 era systems, but most of those other than RHEL/CentOS 6 have already hit the end of their respective support periods.
* Add PEP-0604 to describes an extension to Python language, which aims to add a complementary
syntax to write ``Union[X,Y]`` and ``Optional[X]`` easier.
* Add sample with metaclass with __invert__ and/or __or__
* Remove operator __revert__
* Change title of pep-604
Uses static last stable version tag (v0.11.1), instead of dynamic
branch name (develop), when pointing to documents in the TUF
repository. This makes them more prone to become outdated but less
prone to 404.
Note, that the two referenced tuf publications are also available
under more permanent, albeit paywalled DOIs:
[2] https://doi.org/10.1145/1866307.1866315
[13] https://doi.org/10.1145/1455770.1455841
* Add PEP-0604 to describes an extension to Python language, which aims to add a complementary
syntax to write ``Union[X,Y]`` and ``Optional[X]`` easier.
* Add sample with metaclass with __invert__ and/or __or__
* Remove operator __revert__
Add a new struct_size field to PyPreConfig and PyConfig structures to
allow to modify these structures in the future without breaking the
backward compatibility.
Remove _config_version fields, replaced by struct_size.
Facebook Research has now funded implementation of
cryptographic signing of packages on PyPI. Per
https://github.com/pypa/warehouse/issues/5247#issuecomment-535278176
this means that PEP 458 now moves out of Deferred
status and into Draft status.
Since the PEP was created, the BDFL-Delegate for
PyPI-related PEPs has shifted, and Donald Stufft
is now the Delegate.
* Remove stray reference to `ht_moduleptr`
* Update copyright info
* Remove the new slot for offsets
* Remove note on removed internal functions
* Remove stray reference to Py_TPFLAGS_HEAP_IMMUTABLE
The PEP's previous handling of the micro version compatibility
testing question really wasn't very good, and didn't address the
question of pickle compatibility at all.
So if this idea is going to be considered seriously, it needs
to provide a way to explicitly opt out of the feature additions,
without having to downgrade back to an earlier point release.
* Rewrite section on passing the "defining class" into C methods.
* Remove proposal for immutable heap exception types. Let's leave those to another PEP
* Restrict METH_METHOD to a single calling convention.
This calling convention should be efficient, so also reduce the Optimization section.
* Set names in monospaced font
* Use `nargsf` for the vectorcall "number of args + flag" argument
* Link "per-module state" to the terminology section
* Adjust link to Marcel's current implementation
* Other minor rewordings
https://github.com/python/peps/pull/1159
Nick Coghlan
Guido van Rossum
Brandt Bucher
Ned Deily
Łukasz Langa
Esun Kim
Victor Stinner
Philippe PRADOS
Victor Stinner
lukpueh
Dustin Ingram
Sumana Harihareswara
Bartosz Cierocki
Bruce Merry
Damien George
Philippe PRADOS
Moshe Kaplan
Barry Warsaw
Petr Viktorin
Anthony Sottile
Yury Selivanov
Ezio Melotti
Stefan Behnel
Huong Minh Luu
Laurie O