In the bi-weekly dev meeting today we agreed that deliberate higher-level discussions of datatree's design would be useful. (i.e. we're not worried about our ability to write high-quality code, so let's focus review time more explicitly on the high-level design questions.)
This could take the form of me just talking through what I did in a certain part of the code and why, or a targeted discussion on specific design questions that I was never quite sure about. Some examples of the latter, as food for thought:
dt.ds
ugly? See also the difference between dt.ds
and dt.to_dataset()
Tree linkage + dataset in one object nonideal for UI tree view xarray-contrib/datatree#303 (comment)__contains__
and __getitem__
xarray-contrib/datatree#240xr.concat
/xr.merge
accept DataTree
objects? (and map over them by default?) Support DataTree in Xarray's top level functions #9106There was also this design doc I wrote at one point
@flamingbear are you free at 11:30am EST on Tuesday each week? @shoyer, @keewis and I are all free then. Others also welcome (e.g. @owenlittlejohns , @eni-awowale, @etienneschalk), but not required :)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4