Let’s start by pointing out the differences and determining how it could cause troubles. Here is the code of async and “sync” componentDidMount() life-cycle method: // This is typescript code componentDidMount(): void { /* do something */ } async componentDidMount(): Promise<void> { /* do something */ /* You can use “await” here */ } By … Read more
Okay, I finally have a real answer. I sort of worked it out on my own, but only after Lucian Wischik from the VB part of the team confirmed that there really is a good reason for it. Many thanks to him – and please visit his blog (on archive.org), which rocks. The value 0 … Read more
The async support as specified by google is achieved using two parts: using script on your page (the script is supplied by google) to write out a <script> tag to the DOM. that script has async=”true” attribute to signal to compatible browsers that it can continue rendering the page. The first part works on browsers … Read more
You can use dispatch groups to fire an asynchronous callback when all your requests finish. Here’s an example using dispatch groups to execute a callback asynchronously when multiple networking requests have all finished. override func viewDidLoad() { super.viewDidLoad() let myGroup = DispatchGroup() for i in 0 ..< 5 { myGroup.enter() Alamofire.request(“https://httpbin.org/get”, parameters: [“foo”: “bar”]).responseJSON { … Read more
Why does response.json return a promise? Because you receive the response as soon as all headers have arrived. Calling .json() gets you another promise for the body of the http response that is yet to be loaded. See also Why is the response object from JavaScript fetch API a promise?. Why do I get the … Read more
The difference is that in the first example, the program will block in the first line. The next line (console.log) will have to wait. In the second example, the console.log will be executed WHILE the query is being processed. That is, the query will be processed in the background, while your program is doing other … Read more
Best practice is to mark function async void only if it is fire and forget method, if you want to await on, you should mark it as async Task. In case if you still want to await, then wrap it like so await Task.Run(() => blah())
Note The below answer is not applicable to requests v0.13.0+. The asynchronous functionality was moved to grequests after this question was written. However, you could just replace requests with grequests below and it should work. I’ve left this answer as is to reflect the original question which was about using requests < v0.13.0. To do … Read more
Something like: import threading thr = threading.Thread(target=foo, args=(), kwargs={}) thr.start() # Will run “foo” …. thr.is_alive() # Will return whether foo is running currently …. thr.join() # Will wait till “foo” is done See the documentation at https://docs.python.org/library/threading.html for more details.
If it “doesn’t care about the output”, couldn’t the exec to the script be called with the & to background the process? EDIT – incorporating what @AdamTheHut commented to this post, you can add this to a call to exec: ” > /dev/null 2>/dev/null &” That will redirect both stdio (first >) and stderr (2>) … Read more