Opened 11 years ago
Closed 11 years ago
#22732 closed Uncategorized (needsinfo)
MySQL-for-Python-3 is not actively maintained.
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Python 3 | Version: | 1.6 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
https://docs.djangoproject.com/en/dev/ref/databases/#id8 says:
At the time of writing, the latest release of MySQLdb (1.2.4) doesn’t support Python 3. In order to use MySQLdb under Python 3, you’ll have to install an unofficial fork, such as MySQL-for-Python-3.
This port is still in alpha. In particular, it doesn’t support binary data, making it impossible to use django.db.models.BinaryField.
MySQL-for-Python-3 has not maintained for long time.
I've forked MySQLdb and support Python 3. It support binary.
Could you try mysqlclient and promote it instead of MySQL-for-Python-3?
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Closing for now, pending mailing list discussion.
Note:
See TracTickets
for help on using tickets.
I think we are more likely to recommend/switch to Oracle's MySQL Connector backend (#12500), but the situation probably needs discussion on the django-developers mailing list.