ASSETS_LOAD_PATH is not defined (when installing from pip)
liamcurry opened this issue · comments
Note: I got this error when installing from pip. After I got done writing this I decided to install from github just to check. Turns out I don't get this error anymore (although now I'm trying to figure out how to get this working with S3/Cloudfront), but I figured I'd post this issue anyway just as a reminder to update pip, and for anyone else who may be running into this problem.
Everything works as expected when DEBUG = True, but when switching to DEBUG = False I get an error that looks like this:
KeyError: "Django settings doesn't define load_path
I've gotten this kind of error in the past and to solve I've had to add the setting (in this case, ASSETS_LOAD_PATH) to my Django settings, but that isn't working for me. Unfortunately there seems to be no default set for this in settings.py, and additionally there seems to be no documentation for this setting, so I'm stuck guessing what it actually does. I have defined ASSETS_LOAD_PATH in my Django settings to a variety of values and nothing changes. Here is the file I believe is causing the issues. I installed this from pip.
Yes, this is fixed, its high-time I push a new release to PyPI.