>> There is the recent flurry around the new async additions to python > > I meant to add: “… which I dont pretend to understand…”
Try these links on for size: https://msdn.microsoft.com/en-us/library/hh242982(v=vs.103).aspx which links to https://msdn.microsoft.com/en-us/library/hh242983(v=vs.103).aspx near the end. That summarizes the conceptual difference pretty well imho. It's also summarized on the .NET versions GitHub page: https://github.com/Reactive-Extensions/Rx.NET#a-brief-intro I think you can summarize RX as a framework whereas async/await can be used without significant buy-in (Overlook the "async top down or none at all" best practice sound bite). That is, you can artificially convert a synchronous method into a threaded operation and have it executely asynchronously while you do something else and wait on it for completion at somne other time. However, I have only used the .NET implementations. jlc -- https://mail.python.org/mailman/listinfo/python-list
