Opened 12 months ago
Closed 12 months ago
#34986 closed Bug (fixed)
Fix up support for PyPy 3.10
Reported by: | Nick Pope | Owned by: | Nick Pope |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | pypy |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Python 3.10 support was released in PyPy v7.3.12 in June 2023.
It was highlighted here that a number of tests are failing, and here and here that the changes in #31262 have introduced some large "regressions". It turns out that there is a bug in PyPy related to abstract base classes being used for isinstance()
checks with structural pattern matching. This can be resolved by either waiting for a fix in PyPy or implementing a workaround by removing the pattern matching approach. Aside from that, however, there are also a number of other failures and crashes that still need to be addressed.
PyPy claims to be highly compatible with CPython and that it supports Django. Django claims to be compatible with PyPy. We need to determine whether it is possible to fix these issues or whether we need to remove this claim.
One of the issues is that currently there is no CI to ensure that PyPy support remains in a working state. An initial PR has been created to run a daily scheduled test run on SQLite only. Later it may make sense to enable triggering testing via assigning a label to a PR.
Change History (18)
comment:1 by , 12 months ago
Component: | Uncategorized → Core (Other) |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 12 months ago
Has patch: | set |
---|
comment:14 by , 12 months ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:18 by , 12 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
PR