Provisionally accepted PEPs are currently marked in the PEP repo as simply "Accepted".
This doesn't cause any major problems for CPython, as the only real difference is that the PEP doesn't get marked as Final until the "Provisional" markers get removed from the module documentation.
It's a bit more of an issue for distutils-sig, as our provisionally accepted PEPs may need to be implemented in multiple tools, and the purely informational PEPs may end up going to the Active status rather than to Final the way normal standards track PEPs do.
Having Provisional as a defined state for both Standards Track and Informational PEPs (and updating the PEP 0 listing accordingly) would allow such cases to be handled in a more transparent manner, rather than relying on written notes in the PEP body, or folks having seen the appropriate posts to distutils-sig about it.
Items a PR will need to cover
pep2html.py to handle the new status (no changes needed)Discussions-to: distutils-sig PEPs (I now feel PEP 1 shouldn't be aware of this level of detail)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