Hey Jeremy, Russ,
I've created the working signal now. I have no issue moving the signal to
the django.db.models.signals. However, I never planed on sending the models
set to be created. I felt that would be an apparent miss direction of the
interface. The developer would assume that they'll get
Hi Joseph,
There's no logic that does any such thing. There's nothing unusual or
Django-specific going on here - it's just how Python imports work.
There is a module called django.core.signals. It contains the definitions
for a bunch of signals related to the core operation of Django, like the
'c
I'm not sure what you mean by "maps to".
The basic signal framework is in django.dispatcher. If you're
implementing https://code.djangoproject.com/ticket/11398 then you
probably want to import: from django.dispatcher import Signal.
django.db imports django.core.signals because it is a *consumer*
Hey all,
I'm working on adding that pre_syncdb signal, I've come across a
rother peculiar detail. When I import django.db.signals, it maps to
django.core.signals. Am I missing something here? I know for example,
django.conf generates the settings import. Can someone point me to tho
logic o
