#16968 closed Bug (needsinfo)
Cannot use runserver without definig default database
Reported by: | Yaşar Arabacı | Owned by: | nobody |
---|---|---|---|
Component: | Core (Management commands) | Version: | dev |
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
Hi,
In latest source, you cannot use runserver command without defining a default database settings because django.core.management.validation imports django.db. I thought this may be a design decision, but I am opening a ticket just in case it is not.
Change History (2)
comment:1 by , 13 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
I guess there was something in my installed apps that needed to use database in the time I was trying to runserver. Ticket can be closed.
Note:
See TracTickets
for help on using tickets.
Hi yasar!
Is it possible that you provide more info concerning the issue because it actually works for me doing the following:
Plus browsing to http://127.0.0.1:8000/ provides some useful information telling that you can actually run a django instance without interacting with a db:
If you plan to use a database, edit the DATABASES setting in ticket_16968/settings.py.