PEP 605: add missing word
This commit is contained in:
parent
94935dcd36
commit
f7a85c2640
|
@ -19,8 +19,9 @@ Rather than proposing more frequent full CPython releases (as PEP 602 does),
|
|||
or a policy change to allow backwards compatible feature additions later in a
|
||||
release series (as PEP 598 does), this PEP instead proposes that we create a
|
||||
rolling stream of production-ready beta releases, together with alpha releases
|
||||
that are specifically to be suitable as platforms for building extension modules
|
||||
and wheel archives that are compatible with the subsequent beta releases.
|
||||
that are specifically designed to be suitable as platforms for building
|
||||
extension modules and wheel archives that are compatible with the subsequent
|
||||
beta releases.
|
||||
|
||||
The key desired outcome of this proposal is that the usage guidance given for
|
||||
beta releases would become "suitable for production use only in environments
|
||||
|
|
Loading…
Reference in New Issue