Opened 2 hours ago
Closed 2 hours ago
#36123 closed Cleanup/optimization (wontfix)
Remove reference to PyPy
| Reported by: | Paolo Melchiorre | Owned by: | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | pypy |
| Cc: | Mariusz Felisiak | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
We removed PyPy support in commit f5772de, since there is no version of PyPy compatible with the minimum Python version currently supported (Python 3.12).
To avoid confusion for users, I propose to remove references to PyPy in the documentation, making it very explicit in the release notes that Django 6.0 does not support PyPy.
I believe there are still some references to PyPy in Django code that could be removed.
Of course, we may reinstate support when a version of PyPy compatible with Python 3.12+ is released (I don't think there will realistically be a version of PyPy compatible with Python 3.12 before Django 6.0 is released).
Note:
See TracTickets
for help on using tickets.
This was discussed as part of the PR and was decided against
Unless we plan on "giving up" on PyPy, removing all references and adding them back in will cause quite an additional maintenance burden between releases
If you're in favor of no longer supporting PyPy, I think that will require a forum discussion