[Django] #36123: Remove reference to PyPy

[Django]

#36123: Remove reference to PyPy
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Type:
| Cleanup/optimization
Status: new | Component:
| Documentation
Version: dev | Severity: Normal
Keywords: pypy | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
We removed PyPy support in commit
[https://github.com/django/django/commit/f5772de69679efb54129ac1cbca3579b512778af
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).
--
Ticket URL: <https://code.djangoproject.com/ticket/36123>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#36123: Remove reference to PyPy
-------------------------------------+-------------------------------------

Reporter: Paolo Melchiorre | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution: wontfix

Keywords: pypy | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Sarah Boyce):

* cc: Mariusz Felisiak (added)
* resolution: => wontfix
* status: new => closed

Comment:

This was discussed as part of the
[https://github.com/django/django/pull/19067#discussion_r1922114355 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
--
Ticket URL: <https://code.djangoproject.com/ticket/36123#comment:1>

[Django]

#36123: Remove reference to PyPy

--------------------------------------+------------------------------------

Reporter: Paolo Melchiorre | Owner: (none)

Type: Cleanup/optimization | Status: new

Component: Documentation | Version: dev
Severity: Normal | Resolution:

Keywords: pypy | Triage Stage: Accepted

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

--------------------------------------+------------------------------------
Changes (by Carlton Gibson):

* resolution: wontfix =>
* stage: Unreviewed => Accepted
* status: closed => new

Comment:

The Steering Council discussed this on Monday, 5 October 2026 and think
that we should proceed with removing the references to PyPy at this time.

As per #37363 the recent PyPy version just **added** support for Python
3.12, so the project isn't dead, but we're on the verge of making Python
3.14 the minimum supported version. PyPY is significantly behind where we
need it to be. (It also seems that PyPy is slowly losing mindshare, with
much of the energy in the space being taken by CPython's JiT efforts.)

We discussed various caveats or weakenings to the phrasing about support
but ultimately felt that just removing the references is cleaner.

Re-adopting PyPy would need **something like** them to be compatible with
the most recent two versions of Python, matching Django's support from
Django 2028, **and** there be people actively testing and ensuring PyPy
compatibility with Django. If such comes to pass, we could discuss again
then.
--
Ticket URL: <https://code.djangoproject.com/ticket/36123#comment:2>

[Django]

#36123: Remove reference to PyPy
--------------------------------------+------------------------------------
Reporter: Paolo Melchiorre | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: pypy | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by Vaibhav Pant):

Hello! I'd be glad to work on this ticket, if that's alright.

PR #22086 was closed automatically because the ticket wasn't yet Accepted
when it was opened. @muhammad-a-dev, if you're planning to resubmit, I'd
be happy to step aside or help review. Otherwise, would it be okay if I
took this on? I'd cover the docs and the remaining code references
(`django.utils.version.PYPY` and the PyPy branches in the tests and
`django.test.utils`).

Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/36123#comment:3>