[gentoo-python] recent trend of django-foo tests

[IAN DELANEY <della5@iinet.com.au>]

Am generally reluctant to enter things here, however this issues
appears apt.  Recent versions of django-xxx packages' test suites  have
made a habit of falling over, which is no surprise in itself, but they
have a new cause.  They all expect to find a setting to SECRET_KEY
which is set in djang.conf.global_settings.

For  while I thought

"${PYTHON}" -c "from django.conf import \
global_settings;global_settings.SECRET_KEY='green'" ${test} 

did the trick but it seems that the ${test} after the import with -c "
" is discarded somehow and never actually run with the attempt to set 
SECRET_KEY='green'.  The output looks as if it was an effective run but
it's not the case.

How this came about, who knows.  The backtrace tells it's expecting a
hard coded entry in the installed global_settings.py.  django has some
other django specific mechanisms for running test suites and setting
settings. Anyone know at least one?  How about patching django itself
to include the setting? (That one I expect goes down like a lead
balloon.)


 
kind regards

Ian Delaney