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* of the core signals request_finished and request_started. You probably want to add to django.db.models.signals rather than django.db in any case. https://github.com/django/django/blob/master/django/db/models/signals.py On Wed, Mar 27, 2013 at 4:06 PM, Joseph Curtin <[email protected]> wrote: > 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 > of these path edits? > > Cheers, > -Joseph Curtin > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
