signals

[jerch]

Second approach to a signal implementation, this time much more light-weight with only 3 simple signals:

• resolver_start to indicate the start of a resolver update
• resolver_update sent immediately after a model bulk update
• resolver_exit to indicate the exit of a resolver update

This lighter implementation exposes the resolver_update signals directly from the ongoing dependency tree update, which has several downsides, like being under a transaction and the state not being fully in sync again. --> Needs proper documentation of the shortcomings.

TODO:

• place start & exit signals on handlers (blocked by through model expansion on m2m fields #177 and not_computed context #179)
• test cases
• docs in the manual

Fixes #56 finally.

[coveralls]

Pull Request Test Coverage Report for Build 16204997570

Details

• 22 of 22 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 95.221%

---

Totals
Change from base Build 16201466741:	0.1%
Covered Lines:	1169
Relevant Lines:	1215

---

💛 - Coveralls