id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
17047	django.db.utils.load_backend gives confusing error for unqualified db backend name	Carl Meyer	Jonas Obrist	"If someone upgrades to trunk/1.4, missed the deprecation warnings, and still has e.g. ""sqlite3"" for a database ENGINE setting, the error message they get is a completely opaque ""ImportError: no module named base""

`load_backend` goes to some lengths to give a helpful error message in the case of a totally bogus backend, but oddly in the case of a backend that is not fully-qualified but does exist, it bails with the comment ""this must be an error in Django itself."" That comment/code is just wrong - it would be easy to add a helpful error message for this case."	Bug	closed	Database layer (models, ORM)	dev	Normal	fixed			Accepted	1	0	0	0	1	0