There shouldn't be any issues using the core signals functionality
provided by Django.
I expect the problem here, is that the helper uses the model and
datastore code provided by the App Engine SDK rather than Django's
built in module class and database logic. Hence when you call put/save
on one of your models, you're executing App Engine specific code, not
Django code, which doesn't fire the signal you are expecting.
Your best option is probably to override the put() method of the
helper's Model and make an explicit call to the Django signal
framework to fire off the signal you are expecting, after the put call
in the super class completes.
Of course if you want to submit a patch to the helpers Model to do
this by default to retain compatibility with Django's model we would
most definitely consider it :)
Cheers
--
Matt Brown
ma...@mattb.net.nz
Mob +353 86 608 7117 www.mattb.net.nz