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

["Nikolaj Sjujskij" <sterkrig@myopera.com>]

Den 2013-05-20 13:05:33 skrev 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'.
  % python -h
    ...
-c cmd : program passed in as string (_terminates option list_)

So ${test} seems to be ignored or misinterpreted.


You could try creating ./global_settings.py in :

     from django.conf import global_settings
     global_settings.SECRET_KEY='green'

     print(global_settings)   # testing purposes!

Now:
  % python -c 'import global_settings'
<module 'django.conf.global_settings' from  
'/usr/lib64/python2.7/site-packages/django/conf/global_settings.pyc'>