1 |
Am generally reluctant to enter things here, however this issues |
2 |
appears apt. Recent versions of django-xxx packages' test suites have |
3 |
made a habit of falling over, which is no surprise in itself, but they |
4 |
have a new cause. They all expect to find a setting to SECRET_KEY |
5 |
which is set in djang.conf.global_settings. |
6 |
|
7 |
For while I thought |
8 |
|
9 |
"${PYTHON}" -c "from django.conf import \ |
10 |
global_settings;global_settings.SECRET_KEY='green'" ${test} |
11 |
|
12 |
did the trick but it seems that the ${test} after the import with -c " |
13 |
" is discarded somehow and never actually run with the attempt to set |
14 |
SECRET_KEY='green'. The output looks as if it was an effective run but |
15 |
it's not the case. |
16 |
|
17 |
How this came about, who knows. The backtrace tells it's expecting a |
18 |
hard coded entry in the installed global_settings.py. django has some |
19 |
other django specific mechanisms for running test suites and setting |
20 |
settings. Anyone know at least one? How about patching django itself |
21 |
to include the setting? (That one I expect goes down like a lead |
22 |
balloon.) |
23 |
|
24 |
|
25 |
|
26 |
kind regards |
27 |
|
28 |
Ian Delaney |