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 6338,Better error message on sqlite3 failure,simeon,simeon,"I recently updgraded my OS and restored my django projects from backup. The django shell worked but when I ran {{{manage.py dbshell}}} I got a exception ending in {{{ File ""/usr/lib/python2.5/site-packages/django/db/__init__.py"", line 48, in runshell = lambda: _import_database_module(_import_path, ""client"").runshell() File ""/usr/lib/python2.5/site-packages/django/db/backends/sqlite3/client.py"", line 6, in runshell os.execvp('sqlite3', args) File ""/usr/lib/python2.5/os.py"", line 354, in execvp _execvpe(file, args) File ""/usr/lib/python2.5/os.py"", line 392, in _execvpe func(fullname, *argrest) OSError: [Errno 2] No such file or directory }}} The astute pythoner notes the 3rd line up tries to execute a call to sqlite3 and the actual error message ""No such file or directory"" is just to indicate that we couldn't execute the sqlite3 binary. It took me a minute to realise that I hadn't yet installed sqlite3 and I was on my way. Should we catch the exception and provide a more explicit error message? See patch - but I don't mind if this is a wontfix. ",New feature,closed,"Database layer (models, ORM)",dev,Normal,duplicate,,,Accepted,1,0,0,1,1,0