html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/444#issuecomment-118436430,https://api.github.com/repos/pydata/xarray/issues/444,118436430,MDEyOklzc3VlQ29tbWVudDExODQzNjQzMA==,3101370,2015-07-03T23:02:52Z,2015-07-03T23:02:52Z,NONE,"@shoyer, there are basically two levels of thread safety for HDF5/h5py. First, the HDF5 library has an optional compile-time ""threadsafe"" build option that wraps all API access in a lock.  This is all-or-nothing; I'm not aware of any per-file effects.

Second, h5py uses its own global lock on the Python side to serialize access, which is only disabled in MPI mode.  For added protection, h5py also does not presently release the GIL around reads/writes.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,91184107