#29926 closed New feature (fixed)
Python 3.8 compatibility
Reported by: | Tim Graham | Owned by: | Mariusz Felisiak |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Python 3.8 final is scheduled for October 2019. This is a tracking ticket for compatibility fixes for Django submitted in the meantime.
Change History (17)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
On MySQL and Python 3.8, there's a deprecation warning coming from https://github.com/python/cpython/commit/d3c72a223a5f771f964fc34557c55eb5bfa0f5a0. It might be a mysqlclient issue rather than something that Django needs to address.
comment:3 by , 6 years ago
The author of the commit you linked to is a contributor to both the mysqlclient
and pymysql
project so I assume that's something they'll handle on their side.
comment:4 by , 5 years ago
Triage Stage: | Someday/Maybe → Accepted |
---|
comment:5 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:12 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
In 803840ab: