That doesn't look like any less code to write than I would via an override approach.
And it's fine to use a signal, of course. I'm a big fan of them in my Satchmo work. Either way, whatever method is used, I think the goal should be not to modify Satchmo's code unless it is in a way that is contributable & usable by Satchmo in general. This enables one to keep a smooth upgrade path with Satchmo as it evolves, and have more maintainable code -- you don't have to go hunting down that part of Satchmo you modified. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
