Re: custom signal fails silently, depending on import path (bug ?)

On Fri, Jan 8, 2010 at 1:41 AM, ssc wrote: > Has anyone ever come across this before ? Could not find anything > related in Trac, but I thought I better ask in here before I file a > bug... If you import a signal, using one particular path to specify the import, you

custom signal fails silently, depending on import path (bug ?)

I use a custom signal in my Django app in signals.py: my_project/ my_app/ signals.py views.py In views.py, if I do 'from signals import my_custom_signal' and send the signal, everything is fine. However, if I do 'from my_app.signals import my_custom_signal' and send the signal, it