This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author bquinlan
Recipients bquinlan, jjdominguezm, pitrou
Date 2012-07-18.15:01:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342623682.05.0.0158748073113.issue13785@psf.upfronthosting.co.za>
In-reply-to
Content
My current thinking is that adding a "state" property probably isn't worth it given the fact that you can construct this yourself and the requirement for a "history" property is too specialized.

The callback idea seams reasonable and sufficient for your use case. I think that you'd probably want to *not* specify that state change that you want i.e. any state change triggers the function.

What do you think?

(BTW, I'm on leave right now so it might take a while to respond)
History
Date User Action Args
2012-07-18 15:01:22bquinlansetrecipients: + bquinlan, pitrou, jjdominguezm
2012-07-18 15:01:22bquinlansetmessageid: <1342623682.05.0.0158748073113.issue13785@psf.upfronthosting.co.za>
2012-07-18 15:01:21bquinlanlinkissue13785 messages
2012-07-18 15:01:20bquinlancreate