Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#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: UI/UX:


I installed the trunk of MySQLdb, and when I run, I get the following message:

Error: No module named mysql.base

I'm on django 1.0.2

Change History (5)

comment:1 Changed 7 years ago by Alex

  • Component changed from Uncategorized to Database layer (models, ORM)
  • milestone set to 1.1
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 7 years ago by Alex

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.

comment:3 Changed 7 years ago by kmtracey

  • Resolution set to duplicate
  • Status changed from new to 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 Changed 7 years ago by kmtracey

Not MysqlDB nor MySQLDB but MySQLdb. I can never remember which letters get capped.

comment:5 Changed 5 years ago by jacob

  • milestone 1.1 deleted

Milestone 1.1 deleted

Note: See TracTickets for help on using tickets.
Back to Top