Re: [Django] #14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.

4 views
Skip to first unread message

Django

unread,
Jun 19, 2014, 9:09:30 AM6/19/14
to django-...@googlegroups.com
#14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.
-------------------------------+--------------------------------------
Reporter: bart.ciszk@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.2
Severity: Normal | Resolution:
Keywords: sqlite3 | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by anonymous):

* status: closed => new
* severity: => Normal
* resolution: worksforme =>
* easy: => 0
* ui_ux: => 0
* type: => Uncategorized


Comment:

Just happened to me - reproducing:
use a model import in __ini__ of an app

from configuration.models import myModel

run the testing suite with sqlite db


get:

django.db.utils.OperationalError: no such table: configuration_myModel

--
Ticket URL: <https://code.djangoproject.com/ticket/14932#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jun 19, 2014, 10:23:23 AM6/19/14
to django-...@googlegroups.com
#14932: Tests failing with SQLite3 on Linux systems; Sites object causing failures.
-------------------------------------+-------------------------------------
Reporter: bart.ciszk@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.2
Severity: Normal | Resolution: fixed
Keywords: sqlite3 app-loading | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):

* keywords: sqlite3 => sqlite3 app-loading
* status: new => closed
* resolution: => fixed


Comment:

It isn't clear which conditions triggered this bug, but it cannot happen
anymore in Django 1.7+, thanks to the app-loading refactor. Now it's
explicitly forbidden to import models in `__init__.py` at the root of an
application.

--
Ticket URL: <https://code.djangoproject.com/ticket/14932#comment:4>

Reply all
Reply to author
Forward
0 new messages