@@ -9,16 +9,6 @@ The interface for querying available package versions and
9
9
retrieving packages from an index server comes in two forms:
10
10
HTML and JSON.
11
11
12
- The HTML format is defined in :pep: `503 `, with the addition of "yank"
13
- support (allowing a kind of file deletion) in :pep: `592 `, specifying
14
- the interface version provided by an index server in :pep: `629 `, and
15
- providing package metadata independently from a package in
16
- :pep: `658 ` and revised in :pep: `714 `.
17
-
18
- The JSON format is defined in :pep: `691 `, with additional fields
19
- added in :pep: `700 `, and revisions around providing package metadata
20
- independently from a package in :pep: `714 `.
21
-
22
12
Base HTML API
23
13
=============
24
14
@@ -935,3 +925,20 @@ Clients consuming the JSON representation of the Simple API **MUST** read the
935
925
:pep: `658 ` metadata from the key ``core-metadata `` if it is present. They
936
926
**MAY ** optionally use the legacy ``dist-info-metadata `` key if it is present
937
927
but ``core-metadata `` is not.
928
+
929
+ History
930
+ =======
931
+
932
+ * September 2015: initial form of the HTML format, in :pep: `503 `
933
+ * July 2016: Requires-Python metadata, in an update to :pep: `503 `
934
+ * May 2019: "yank" support, in :pep: `592 `
935
+ * July 2020: API versioning convention and metadata, and declaring the HTML
936
+ format as API v1, in :pep: `629 `
937
+ * May 2021: providing package metadata independently from a package, in
938
+ :pep: `658 `
939
+ * May 2022: initial form of the JSON format, with a mechanism for clients to
940
+ choose between them, and declaring both formats as API v1, in :pep: `691 `
941
+ * October 2022: project versions and file size and upload-time in the JSON
942
+ format, in :pep: `700 `
943
+ * June 2023: renaming the field which provides package metadata independently
944
+ from a package, in :pep: `714 `
0 commit comments