You shouldn't have any problem adding a signals.py to your project with the added signal code you want to be part of your shop.
You could add it to an existing app that is associated with your store, or create a generic app like 'lib' with a structure like this: lib/ -- __init__.py -- signals.py Then add your simple lib app to INSTALLED_APPS in your project settings.py file. On Sun, Oct 25, 2009 at 11:54 PM, Gloria <[email protected]> wrote: > > Hi all, > > I have this bit of code written to add signals to Satchmo. > Unfortunately the person who wrote it added it to the distro file > itself: > > In /usr/local/lib/python2.6/dist-packages/Satchmo-0.9_p > re-py2.6.egg/payment/signals.py: > > import django.dispatch > > confirm_sanity_check = django.dispatch.Signal() > payment_choices = django.dispatch.Signal() > payment_methods_query = django.dispatch.Signal() > form_save = django.dispatch.Signal() > payment_form_init = django.dispatch.Signal() > payment_form_validation = django.dispatch.Signal() > > > > Three more signals are added here. Is there a better way to register > new signals without changing a file in the distro area? This will get > overwritten with each new release, and the errors it causes when it's > missing are incomprehensible to the average developer. > > Thank you, > Gloria > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
