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 jjdominguezm
Recipients bquinlan, jjdominguezm
Date 2012-01-15.21:02:23
SpamBayes Score 2.272221e-06
Marked as misclassified No
Message-id <1326661344.17.0.708068246784.issue13785@psf.upfronthosting.co.za>
In-reply-to
Content
Hello,

You're right, explaining the difference between CANCELLED and CANCELLED_AND_NOTIFIED is gong to be hard and might be confusing. I also agree that there is no precedent for storing the history of something, and I don't like either the idea of having a futures factory (that was my first idea).

But, what about using callbacks? it is possible to add done callbacks, why can't we have a list of callbacks attached to each "public" state.

Something like:

Future.append_callback(self, state: "One of PENDING, RUNNING, CANCELLED, FINISHED", fn)
History
Date User Action Args
2012-01-15 21:02:24jjdominguezmsetrecipients: + jjdominguezm, bquinlan
2012-01-15 21:02:24jjdominguezmsetmessageid: <1326661344.17.0.708068246784.issue13785@psf.upfronthosting.co.za>
2012-01-15 21:02:23jjdominguezmlinkissue13785 messages
2012-01-15 21:02:23jjdominguezmcreate