Hi Skip, On Tue, May 1, 2012 at 5:58 PM, Skip Montanaro <s...@pobox.com> wrote: > (ame) Is there some reason a more descriptive > name isn't used?
That name was used as a temporary placeholder for a better name :-/ I think that obscure acronyms should be out (including "stm"). Laura's "schedule" was good, but does it still apply? Can you reasonably write "from schedule import atomic"? ... well, maybe, yes. So "schedule" would be the module in which we find at least "atomic", a pair of functions "atomic_start() / atomic_stop()", and the "Runner" class implementing a thread pool. Or maybe, keeping in touch with "concurrent.futures" from Python 3.2, should we make it "nonconcurrent.schedule"...? :-) A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
