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 pablogsal
Recipients belopolsky, christian.heimes, eric.smith, gdr@garethrees.org, lukasz.langa, martin.panter, orsenthil, pablogsal, remi.lapeyre, rhettinger, terry.reedy, tim.peters, tshepang
Date 2020-01-15.01:24:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579051459.94.0.350624914779.issue17005@roundup.psfhosted.org>
In-reply-to
Content
> Am I seriously suggesting this for Python?  Sure.  It's fun to advance the practical state of the art :-)


I think this API looks very interesting! I have some questions before start implementing it to play a bit with it:

- I am slightly confused about what .prepare() should do. Why is this step necessary?

- Why we need the .done() method here? Why not instead make get_ready() simply a generator so you can just write

    for node in self.get_ready():

It seems that the .done() is very tight to use this API as a "task scheduler" but maybe I am doing something here in
my understanding of the API.
History
Date User Action Args
2020-01-15 01:24:20pablogsalsetrecipients: + pablogsal, tim.peters, rhettinger, terry.reedy, belopolsky, orsenthil, eric.smith, christian.heimes, lukasz.langa, tshepang, gdr@garethrees.org, martin.panter, remi.lapeyre
2020-01-15 01:24:19pablogsalsetmessageid: <1579051459.94.0.350624914779.issue17005@roundup.psfhosted.org>
2020-01-15 01:24:19pablogsallinkissue17005 messages
2020-01-15 01:24:19pablogsalcreate