GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Include the PEP index in `peps.json` by wookie184 · Pull Request #2567 · python/peps

Conversation

@wookie184

@wookie184 wookie184 commented May 1, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

pep 0 is a bit different from other peps given that it's autogenerated, but I still think it makes sense to include it in the api/peps.json endpoint.

Page in build preview: https://pep-previews--2567.org.readthedocs.build/api/peps.json

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
hugovk reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@wookie184
Include pep 0 in api/peps.json
0bac7bd
@wookie184
wookie184 requested a review from AA-Turner as a code owner May 1, 2022 12:46
AA-Turner
AA-Turner approved these changes May 1, 2022
View reviewed changes
@AA-Turner AA-Turner changed the title Include pep 0 in api/peps.json Include the PEP index in peps.json May 1, 2022
@AA-Turner
AA-Turner merged commit 278070a into python:main May 1, 2022
@AA-Turner

AA-Turner commented May 1, 2022

Copy link
Copy Markdown
Member

Thanks, PEP 0 is still a PEP so should be included (although fair enough to exclude PEP 0 from itself!)

A
hugovk reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@CAM-Gerlach CAM-Gerlach added the infra Core infrastructure for building and rendering PEPs label May 3, 2022
@AA-Turner AA-Turner mentioned this pull request May 7, 2022
Document peps.json and move it to the root #2584
Closed
@erlend-aasland erlend-aasland mentioned this pull request May 13, 2022
pep8/greppable exception messages erlend-aasland/peps#1
Closed
@erlend-aasland erlend-aasland mentioned this pull request Jun 27, 2022
pep 687/mark as accepted erlend-aasland/peps#2
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AA-Turner AA-Turner AA-Turner approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

infra Core infrastructure for building and rendering PEPs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@wookie184 @AA-Turner @CAM-Gerlach
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.