Cannot use a settings file outside of my project package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Django Recipe |
New
|
Undecided
|
Unassigned |
Bug Description
I want to use the djangorecipe's manage.py wrapper and the test script in a new
created django app.
I have the following directory structure:
src/
app/
buildout.cfg
testsettings.py
And here is the django part of my buildout.cfg:
[django]
recipe = djangorecipe
version = 1.1.1
project = app
projectegg = app
settings = testsettings
test = app
eggs =
extra-paths =
src
Unfortunatelly djangorecipe will fail here. It will not find my settings file
correctly, because it always prepends the settings module name with the project
name which results in `app.testsettings` in this case. This not a good
behaviour and is limiting my project layout. Ofcourse i considered moving the
testsettings.py file into the app direcotry, but I think it is no good habit
for a django app to ship with its own settings file.
Just give me nice hint if I have overlooked an option that makes djangorecipe
behave the way which is needed in this case.
Thanks for your clear report. I am afraid that there currently is no work-around for this. It should be possible to introduce an option to disable the prepending of the application. A patch to make this happen would be greatly appreciated.