#10682 closed (duplicate)
The latest MySQLdb breaks Django
| Reported by: | twleung | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.0 |
| Severity: | 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
I installed the trunk of MySQLdb, and when I run manage.py, I get the following message:
Error: No module named mysql.base
I'm on django 1.0.2
Change History (5)
comment:1 by , 15 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|---|
| milestone: | → 1.1 |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 15 years ago
comment:3 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Django hasn't run on "latest trunk" MysqlDB for a long time. There is some considerable restructuring going on in that code and until it gets near to a release point it doesn't seem to make a lot of sense to chase it. #9274 is open to track whatever needs to be done to get Django running on the next release of MySQLDB.
comment:4 by , 15 years ago
Not MysqlDB nor MySQLDB but MySQLdb. I can never remember which letters get capped.
Note:
See TracTickets
for help on using tickets.
I can't find any references to mysql.base in Django, can you post a full traceback so we can make sure it's not an issue with MySQLdb.