#26023: Importing GenericForeignKey on Django 1.9
-------------------------------------+-------------------------------------
Reporter: Chris7 | Owner: nobody
Type: Bug | Status: new
Component: | Version: 1.9
contrib.contenttypes |
Severity: Normal | Resolution:
Keywords: generic foreign | Triage Stage:
keys | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris7):
The case is for the app [https://github.com/wooey/Wooey/ Wooey] and this
[https://github.com/wooey/Wooey/issues/101 issue].
We have an option that bootstraps the installation process which entails
setting up Django project with pre-determined settings. For compatibility
with older versions of Django, there is a compatibility shim to handle
cases like GFK's import location being changed and the template engine's
get_string method. So at the onset, there is no INSTALLED_APPS. It's a
python script importing GFK. I could move these imports to another shim
(or do some other workarounds) but this approach works in other Django
versions -- although it could entirely be fortunate this behavior was not
flagged.
--
Ticket URL: <https://code.djangoproject.com/ticket/26023#comment:3>
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/064.5ac4c05ecaa657e0c5a649f87eed6a3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
