#20704: DATABASE_ROUTERS : ImproperlyConfigured "cannot import name connection"
-------------------------------------+-------------------------------------
Reporter: artscoop | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: router | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* resolution: => worksforme
Comment:
Thanks for testing on latest code, and I'm happy this is fixed there.
I think you should be able to temporarily workaround the problem by moving
your custom Router class in a different path. The current circular import
issue may be caused by any `__init__.py` along the path (i.e.
`engine/__init__.py`, `engine/db/__init__.py`, etc.).
I really doubt that the fix will be backported in 1.5, therefore closing
the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/20704#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4dfc53a40a269662c777aae1dd86d855%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.