Skip to content

PEP691: Switch to a List for Project, Address more Feedback #2653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dstufft merged 7 commits into from
Jun 17, 2022
Merged

PEP691: Switch to a List for Project, Address more Feedback #2653

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
cb73180
Clarify that No Accept equals Accept: */*
dstufft Jun 17, 2022
bbc8583
Clarification + Move Index to an array
dstufft Jun 17, 2022
e940b0c
Add the underlying data models for the Simple API
dstufft Jun 17, 2022
ca081aa
whitespace
dstufft Jun 17, 2022
7c996e6
Add a FAQ about versioning
dstufft Jun 17, 2022
a81ea27
Better phrasing
dstufft Jun 17, 2022
b8e887d
Spelling
dstufft Jun 17, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Better phrasing
  • Loading branch information
@dstufft
dstufft committed Jun 17, 2022
commit a81ea2742e4f4e7786d163ac606329c22f5bc1ba
19 changes: 10 additions & 9 deletions pep-0691.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -946,17 +946,18 @@ how they use the Simple + JSON APIs today or how they currently plan to use it:
Appendix 2: Rough Underlying Data Models
========================================

These are not exact, as these models do not actually exist anywhere, and
are instead best thought of as the conceptual, underlying data model that
backs each of these API responses throughout the number of PEPs that have
modified the repository API since it's inception.

The existing HTML, and the JSON serializations of these data models then
represents how these underlying concpetual models get mapped onto the
These are not intended to perfectly match the server, client, or wire
formats. Rather, these are concpetual models, put to code to make them
more explicit as to the abstract models underlining the repository API
as it evolved through :pep:`503`, :pep:`529`, :pep:`629`, :pep:`658`,
and now this PEP, :pep:`691`.

The existing HTML, and the new JSON serialization of these models then
represent how these underlying concpetual models get mapped onto the
actual wire formats.

Project Index
-------------
How servers or clients choose to model this data is out of scope for
this PEP.

.. code-block:: python

Expand Down