You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For PEPs which have a target Python version, PEP 0 could link the Python version number to the release PEP for that version. That would make it a little nicer when you text search PEP 0 for say, "3.14" and want to find PEP 745. E.g. since PEP 761 comes before PEP 745 textually on the page (because the former is a Process PEP), your first textual search hit lands on the "3.14" in the last column for the PEP 761 row. If I could click on that and get to PEP 745, that would save me a minuscule but perceptible hassle!
The text was updated successfully, but these errors were encountered:
For PEPs which have a target Python version, PEP 0 could link the Python version number to the release PEP for that version. That would make it a little nicer when you text search PEP 0 for say, "3.14" and want to find PEP 745. E.g. since PEP 761 comes before PEP 745 textually on the page (because the former is a Process PEP), your first textual search hit lands on the "3.14" in the last column for the PEP 761 row. If I could click on that and get to PEP 745, that would save me a minuscule but perceptible hassle!
The text was updated successfully, but these errors were encountered: