This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Mike,
I'm submitting this pull request because of trouble I had while using django medusa with Django 1.8. Django 1.7 added the concept of applications where you define an
AppConfig
class. You have the option of using a path to the class inINSTALLED_APPS
, as explained in the docs:This is a problem in
django_medusa.utils
because it assumes everything inINSTALLED_APPS
is a module path, not a class path. I worked around this, keeping the code almost entirely the same by using thedjango.apps.get_apps_config()
method to get a list of apps django has loaded fromINSTALLED_APPS
and getting the string name of the module from there. From what I can tell this should be backwards compatible with Django < 1.7 but I have not used it that way myself.