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 tim.peters
Recipients Dennis Sweeney, eric.smith, larry, pablogsal, tim.peters
Date 2022-03-31.00:02:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Various kinds of tasks:

- "Power switch must be on." Needs to done the first time. _May_ need to be done again later (if some later task turns the power off again). Can be done any number of times without harm (beyond the expense of checking), so long as the switch is on.

- "Ensure gas tank is full." Probably needs to be done anew for every new added task that depends on it.

- "Remove outermost layer of skin." Probably shouldn't be done more than once ;-)

- "Flip Najdorf switch." Who knows? Doing it a second time - or failing to do it a second time - may be necessary, harmless, or deadly.

I'd rather not bother with any of this dicey guessing. While some dynamism may be attractive, what it all "should mean" appears to be a rat's nest, and depends on domain knowledge graphlib can't possibly have.

I doubt there is a compelling default. As is, two tasks are considered to be "the same" task if and only if they compare equal, so that's the least _surprising_ default for tasks added later. "Remove outermost layer of skin"

"Two tasks that compare equal may or may not be considered the same task, depending on the execution history at the time the question is posed" is at best expedient, at worst disastrous.
Date User Action Args
2022-03-31 00:02:25tim.peterssetrecipients: + tim.peters, larry, eric.smith, pablogsal, Dennis Sweeney
2022-03-31 00:02:25tim.peterssetmessageid: <>
2022-03-31 00:02:25tim.peterslinkissue47145 messages
2022-03-31 00:02:24tim.peterscreate