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 Joshua.Harlow
Recipients Joshua.Harlow
Date 2015-06-14.17:16:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It would be quite useful to have some types of metrics attached to future objects so that callers could use them for various activities (scheduling repeated runs, post-analysis and such):

Some of the ones that I can think would be useful:

- 'submitted_at' (when the callback was submitted to the executor responsible for executing it)
- 'started_at' (when the executor actually started executing the callback, which is typically sometime after it was submitted)
- 'finished_at' (when the executor finished calling the callback)
- elapsed [finished_at - started_at] (the elapsed runtime of the callback)

Do others feel this would be useful (if so I can put up some patches)? Right now getting this information is pretty hard to get at (since the executors that exist currently do not expose this information and it is quite hard to obtain it in a reliable manner).
Date User Action Args
2015-06-14 17:16:11Joshua.Harlowsetrecipients: + Joshua.Harlow
2015-06-14 17:16:11Joshua.Harlowsetmessageid: <>
2015-06-14 17:16:11Joshua.Harlowlinkissue24451 messages
2015-06-14 17:16:11Joshua.Harlowcreate