-
Notifications
You must be signed in to change notification settings - Fork 88
Prefer simple JSON when possible #1372
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.
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Prefer the PyPI Simple API JSON response when clients such as pip and uv advertise JSON alongside HTML. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 14535
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 3369
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 7141
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 3887
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 7754
🌐 Web query:
DRF 3.15.2 rest_framework negotiation.py _MediaType q quality parameter source💡 Result:
In Django REST Framework (DRF) version 3.15.2, the negotiation logic within rest_framework/negotiation.py does not natively utilize the 'q' (quality) parameter from the HTTP 'Accept' header to influence renderer selection [1][2]. Historically, DRF's default content negotiation has operated by prioritizing media type specificity and the order of renderers defined in the settings, explicitly opting not to implement 'q' value weighting [1][3]. The _MediaType class and associated utilities are responsible for parsing media types, but they have traditionally focused on precedence rather than quality-weighted preference [4][2]. It is important to note that while some community discussions and recent developments indicate interest or efforts to change this behavior (such as commit 7961497 which surfaced in mid-2026 to honor 'q' values) [5], version 3.15.2 maintains the established behavior where 'q' values are not used [1][3]. If your specific environment or a patch has introduced this, it deviates from the long-standing core design documented in the official DRF content negotiation guide [1][3]. For developers requiring RFC-compliant 'q' value weighting, the recommended approach remains implementing a custom content negotiation class by overriding BaseContentNegotiation [1][3].
Citations:
🏁 Script executed:
Repository: pulp/pulp_python
Length of output: 2440
Do not prioritize JSON when the client sets
q=0.In
SimpleView.get_renderers, the substring check matchesapplication/vnd.pypi.simple.v1+json;q=0and putsPyPISimpleJSONRendererfirst. DRF 3.15.2 does not useqvalues during matching, so it can return JSON even though the client excludes it. Parse the media ranges and skip the JSON-first override when JSON has quality0. Add this header as a regression case inpulp_python/tests/functional/api/test_pypi_simple_api.py.🤖 Prompt for AI Agents