pull_requests
71 rows where user = 10050469
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date), merged_at (date)
| id ▼ | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 50391159 | MDExOlB1bGxSZXF1ZXN0NTAzOTExNTk= | 655 | closed | 0 | More control on cmap params | fmaussion 10050469 | **Motivation:** https://github.com/xray/xray/issues/642 User's `vmin`, `vmax` are no longer overwritten. You can prevent divergent cmaps and keep automatic vmin, vmax bei setting `center=False`. This is quite intuitive I think (first thing I tried when I wanted to avoid a divergent colormap). See the new tests for examples of use. | 2015-11-11T14:51:10Z | 2015-11-15T22:20:04Z | 2015-11-15T22:19:05Z | 2015-11-15T22:19:05Z | a9b1b821c1a6fdce709cc66fe1c520be5a041ceb | 0 | 9bf93f79194ecfd512b6e947f39e91c654d7f205 | 5109f4f7bcb08c03ba006d42bed906ff0d194a29 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/655 | ||||
| 61156349 | MDExOlB1bGxSZXF1ZXN0NjExNTYzNDk= | 778 | closed | 0 | fix value error in data-structures doc | fmaussion 10050469 | This should fix the error in the docs here: http://xarray.pydata.org/en/latest/data-structures.html It is a detail, but it occurred to me that the examples of this section don't use the (space, time) dimension order (e.g. `dims=['time', 'space']`). Most of the climate datasets I know of are using the numpy (lat, lon, time) dim order. Is it intentional? | 2016-02-29T22:21:58Z | 2016-03-01T00:50:27Z | 2016-03-01T00:50:27Z | 2016-03-01T00:50:27Z | 2661aa20e745b14291d55c0b9d7e60720ce434b3 | 0 | b8eaa7cbf6e9fc24e0b80a13301ab81baf60d303 | b15f0ee759248ef52b9a53d410090133b86216ee | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/778 | ||||
| 62641492 | MDExOlB1bGxSZXF1ZXN0NjI2NDE0OTI= | 794 | closed | 0 | fix: transpose non-linked coordinates in 2d plots | fmaussion 10050469 | Should fix https://github.com/pydata/xarray/issues/788 | 2016-03-12T13:32:59Z | 2016-03-13T20:06:02Z | 2016-03-13T20:06:02Z | 2016-03-13T20:06:02Z | ec94594de16bbdb6b228718fb36d94872973b4ef | 0 | 83dd5a2bd307071769700d6eae2d1c263bd1c561 | f905289ea750637f655ac6ad659a859bca575ea5 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/794 | ||||
| 72539305 | MDExOlB1bGxSZXF1ZXN0NzI1MzkzMDU= | 868 | closed | 0 | BUG: contour plot levels | fmaussion 10050469 | This should fix https://github.com/pydata/xarray/issues/866 | 2016-06-03T17:10:09Z | 2016-07-20T17:16:28Z | 2016-07-20T17:16:27Z | 2016-07-20T17:16:27Z | 884b247742af2480e269bb54c9102f08c867fdaa | 0 | ff721b6f48ce1d5f35d3f167f766f327d281e223 | 745d976e0bc676342e7e4354f45846fc101c02de | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/868 | ||||
| 72627551 | MDExOlB1bGxSZXF1ZXN0NzI2Mjc1NTE= | 870 | closed | 0 | DOC: mention conda-forge | fmaussion 10050469 | Follow-up on https://github.com/pydata/xarray/issues/869#issuecomment-223776182 I am no native speaker, so feel free to change everything. | 2016-06-05T11:59:45Z | 2016-06-06T20:13:54Z | 2016-06-06T20:13:49Z | 2016-06-06T20:13:49Z | 2448b5b3fa3647419df8f14d60f1c32b9d002af7 | 0 | b5597fa4374ac30b02b810ae8e8570e773878e6d | 80abe5dede7bf8a2949139f8ba083a6d74d4e3db | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/870 | ||||
| 72860302 | MDExOlB1bGxSZXF1ZXN0NzI4NjAzMDI= | 872 | closed | 0 | ENH: more control on colorbar | fmaussion 10050469 | Addresses https://github.com/pydata/xarray/issues/752 and allows to pass kwargs to colorbar. For example, it is now possible to do: ``` python import numpy as np import matplotlib.pyplot as plt import xarray as xr x, y = np.meshgrid(np.arange(12), np.arange(12)) z = xr.DataArray(np.sqrt(x**2 + y**2)) ds = z.to_dataset(name='z') fig, ((ax1, ax2), (ax3, ax4)) = plt.subplots(2, 2, figsize=(12, 12)) ds.z.plot.contourf(ax=ax1) ds.z.plot.contourf(ax=ax2, cbar_kwargs={'orientation':'horizontal', 'label':'MyLabel'}) ds.z.plot.contourf(ax=ax3, cbar_ax=ax4, cbar_kwargs={'orientation':'horizontal', 'label':'Funny Cbar', 'drawedges':True}) plt.tight_layout() plt.show() ```  | 2016-06-07T11:44:52Z | 2017-08-10T15:49:55Z | 2016-06-09T15:52:46Z | 2016-06-09T15:52:46Z | 450ac8fb16bec935a18ff3155673dff82208d3fe | 0 | dc1e3fab1fccae0085641a7bd181d7615c87d3f1 | 2448b5b3fa3647419df8f14d60f1c32b9d002af7 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/872 | ||||
| 86017826 | MDExOlB1bGxSZXF1ZXN0ODYwMTc4MjY= | 1011 | closed | 0 | .where() and .fillna() should preserve attributes | fmaussion 10050469 | Fixes https://github.com/pydata/xarray/issues/1009 There is probably a more elegant way to do it, but the internals of xarray still confuse me. I'm happy to learn! | 2016-09-20T17:11:21Z | 2016-09-21T17:46:28Z | 2016-09-21T17:26:32Z | 2016-09-21T17:26:32Z | c1eddafdee4477099979bc97b22a9c7fe014b793 | 0 | 37c8f37ddc7d1533433ffa81aa0d59ac2dc09dbe | 8ef9aad62760bdca038a32ead22941e76f1e507b | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1011 | ||||
| 86018748 | MDExOlB1bGxSZXF1ZXN0ODYwMTg3NDg= | 1012 | closed | 0 | mini improvement of the install doc | fmaussion 10050469 | cyordereddict is now obsolete | 2016-09-20T17:17:14Z | 2016-09-21T17:46:43Z | 2016-09-20T17:18:39Z | 2016-09-20T17:18:39Z | 8ef9aad62760bdca038a32ead22941e76f1e507b | 0 | 1106198e88052534f617eb06db5b54ab79bb1673 | 551a7bca7b42a6d6db976b01d2eee1131735785d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1012 | ||||
| 89487607 | MDExOlB1bGxSZXF1ZXN0ODk0ODc2MDc= | 1048 | closed | 0 | WIP: preserve variables order in Dataset.concat() | fmaussion 10050469 | addresses https://github.com/pydata/xarray/issues/1042 The problem is that sets aren't ordered. I tried something based on an OrderedSet recipe, but I'm not sure that this is the most elegant way to go. A remaining issue is that the coord variable is still not in place (`['t', 'a', 'b', 'c']` becomes `['a', 'b', 'c', 't']`), but I'm not sure it's possible to do it better (it happens [here](https://github.com/pydata/xarray/blob/master/xarray/core/combine.py#L273-L274)). Any idea welcome | 2016-10-15T09:27:53Z | 2016-10-15T22:50:16Z | 2016-10-15T22:50:16Z | 0d084329c676b74409a9f529feec70c2ad9966cd | 0 | a46c205fe21310d3ff0e81550100e79a0ac5040b | 62a7f2c00caacb5b917ff320e28aca9cb4396649 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1048 | |||||
| 89498325 | MDExOlB1bGxSZXF1ZXN0ODk0OTgzMjU= | 1049 | closed | 0 | Preserve variables order in Dataset.concat() | fmaussion 10050469 | Alternative (and much easier) implementation to https://github.com/pydata/xarray/pull/1048 The problem with the coordinate variables remains the same | 2016-10-15T16:30:32Z | 2016-11-02T01:35:53Z | 2016-11-02T01:35:53Z | 2016-11-02T01:35:53Z | a4f5ec2263ee96059f87daec4c217d425ca94e51 | 0 | cea26bb851aacf29c4991407d4c127d92182615d | 62a7f2c00caacb5b917ff320e28aca9cb4396649 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1049 | ||||
| 90853585 | MDExOlB1bGxSZXF1ZXN0OTA4NTM1ODU= | 1060 | closed | 0 | Remove obsolete NetCDF4 Error catch | fmaussion 10050469 | [edit: this original PR was replaced with another change: "remove obsolete NetCDF4 Error catch"] This allows to give a customized NetCDF4 object to the DataStore. I needed this for Salem's diagnostic variables: https://github.com/fmaussion/salem/blob/master/salem/sio.py#L737-L751 My workaround (a very [shallow](https://github.com/fmaussion/salem/blob/master/salem/sio.py#L653) subclass of NetCDF4DataStore) is fine for me, so I won't be offended if you decide not to merge. On a related issue, the IndexError catch which happens [here](https://github.com/pydata/xarray/blob/master/xarray/backends/netCDF4_.py#L52) is also giving me trouble, since it hides bugs in my code. I know I'm kind of misusing the backend, but I find it very useful the way it is. I'm open to any suggestion to make it more elegant. Thanks! | 2016-10-25T17:25:33Z | 2017-05-22T08:58:21Z | 2017-05-22T08:58:21Z | 1ee3bb85cc5489a1df52e17ad690cd992590b8a7 | 0 | f24e8805b77682a21d086c6e28a8041b79c035b2 | a4f5ec2263ee96059f87daec4c217d425ca94e51 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1060 | |||||
| 92253877 | MDExOlB1bGxSZXF1ZXN0OTIyNTM4Nzc= | 1079 | closed | 0 | New infer_intervals keyword for pcolormesh | fmaussion 10050469 | Addresses https://github.com/pydata/xarray/issues/781 @jhamman what do you think? I'm not sure if ``infer_interval_breaks`` is the best name for the keyword but I didn't come up with anything better than that. (maybe ``infer_coord_intervals``?) | 2016-11-03T22:35:29Z | 2016-11-10T22:55:03Z | 2016-11-10T22:55:03Z | 2016-11-10T22:55:03Z | 8ded25088cbb92bdd588f3e2dcbb0491d280c623 | 0 | b9ec680a8a1e7dbd0a481e9aa518cec09d8a1bee | a4f5ec2263ee96059f87daec4c217d425ca94e51 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1079 | ||||
| 92875526 | MDExOlB1bGxSZXF1ZXN0OTI4NzU1MjY= | 1098 | closed | 0 | Docs tweaks | fmaussion 10050469 | The multidimensional coords example is now built live. I tested this locally and tried to keep the look of the figures as close as possible to the original ones. CC @rabernat @shoyer (I also added a link to salem in the list of packages extending xarray - shameless self-promotion) | 2016-11-08T22:50:34Z | 2016-11-09T20:52:19Z | 2016-11-09T17:44:49Z | 2016-11-09T17:44:49Z | 53994194560772ff926f6661bf143abeedda5b60 | 0 | c013d710acf70bdbcb39bfce9ab33ada691f5a5f | 2a17af77955a11e93fafccdc8bc619adfc9e402a | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1098 | ||||
| 93030342 | MDExOlB1bGxSZXF1ZXN0OTMwMzAzNDI= | 1099 | closed | 0 | Add cartopy and netcdf4 to the doc build | fmaussion 10050469 | as discussed in https://github.com/pydata/xarray/pull/1098 | 2016-11-09T20:10:25Z | 2016-11-09T20:41:04Z | 2016-11-09T20:41:04Z | 2016-11-09T20:41:04Z | 3add6ce8cbefd3b6413179cd32796b32398159f1 | 0 | b079e01157db0abc7945e90f55359411f92d8cbf | 53994194560772ff926f6661bf143abeedda5b60 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1099 | ||||
| 93037270 | MDExOlB1bGxSZXF1ZXN0OTMwMzcyNzA= | 1101 | closed | 0 | unpin package versions for doc build | fmaussion 10050469 | 2016-11-09T20:55:47Z | 2016-11-10T02:44:28Z | 2016-11-09T21:07:01Z | 2016-11-09T21:07:01Z | 92095f759a4b61691bf494d46d8d3008d812c6f8 | 0 | 8e2b2f3188ce41b09309f85208c93364b4d70e37 | 3add6ce8cbefd3b6413179cd32796b32398159f1 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1101 | |||||
| 93177872 | MDExOlB1bGxSZXF1ZXN0OTMxNzc4NzI= | 1105 | closed | 0 | Another attempt to get netCDF4 working on RTD + py3 | fmaussion 10050469 | Sorry @shoyer you might get a few of these debugging PRs today again. | 2016-11-10T15:59:27Z | 2016-11-10T16:50:18Z | 2016-11-10T16:49:42Z | 2016-11-10T16:49:42Z | a7bb97cadc1578da03220115d3cff6718ac6ee25 | 0 | 9e7e04bdd3d38b9f1a5a90dcfc4c1ef4c5e5fbd1 | 92095f759a4b61691bf494d46d8d3008d812c6f8 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1105 | ||||
| 93368255 | MDExOlB1bGxSZXF1ZXN0OTMzNjgyNTU= | 1108 | closed | 0 | py2 compat header | fmaussion 10050469 | As discussed in https://github.com/pydata/xarray/pull/1079 I just left out a couple of nearly empty ``__init__``s I also removed a couple of unused imports | 2016-11-11T17:29:05Z | 2016-11-11T18:01:11Z | 2016-11-11T18:01:06Z | 2016-11-11T18:01:06Z | 10fc0846b1ae86d729ffd855641f4510947085a9 | 0 | 4360c6d6ee8f787ef113b6b979183621c0a24e1b | 57facab09b2e78221ff35e2dfcf05e0c447f769e | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1108 | ||||
| 93374260 | MDExOlB1bGxSZXF1ZXN0OTMzNzQyNjA= | 1110 | closed | 0 | Add default channel to conda on RTD | fmaussion 10050469 | As discussed here: https://github.com/pydata/xarray/issues/1106 I also added a section somewhere to print the packages versions on RTD. It will be useful to pin the versions again once it works, and is useful enough to stay on the docs I think. I just didn't really knew where to put it, other ideas welcome! | 2016-11-11T18:13:25Z | 2016-11-11T18:36:24Z | 2016-11-11T18:36:23Z | 2016-11-11T18:36:23Z | 1ff3a0bdc4e41af88c32803b0f95557f021e2ceb | 0 | ce6537fa89fe5c89770c0429099666c19fbefb6a | 10fc0846b1ae86d729ffd855641f4510947085a9 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1110 | ||||
| 93406633 | MDExOlB1bGxSZXF1ZXN0OTM0MDY2MzM= | 1112 | closed | 0 | Bug in DecodedCFDatetimeArray | fmaussion 10050469 | Fixes https://github.com/pydata/xarray/issues/1111 | 2016-11-11T22:11:22Z | 2016-11-13T18:04:00Z | 2016-11-13T18:04:00Z | 2016-11-13T18:04:00Z | 0ed1e2c93732472ecf4985875982daaccc9fa34c | 0 | c952855db30b743d6c1b2aa4a3116be47d578ab6 | 1ff3a0bdc4e41af88c32803b0f95557f021e2ceb | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1112 | ||||
| 95380441 | MDExOlB1bGxSZXF1ZXN0OTUzODA0NDE= | 1134 | closed | 0 | Further attempt to get netCDF4 working on RTD | fmaussion 10050469 | The idea came from here: https://github.com/Unidata/netcdf4-python/issues/574#issuecomment-235435628 I could test it on another repo, so I'm confident that this should work here too. Obviously, this is a temporary solution. hopefully fixes https://github.com/pydata/xarray/issues/1106 | 2016-11-26T19:25:45Z | 2016-11-28T11:11:24Z | 2016-11-26T21:48:40Z | 2016-11-26T21:48:40Z | b72d894154e182e90b56c76ac24d77d8f4a0677d | 0 | d85b096ff48b6c0219125e364cb5fc8aa0a9e195 | 76726e58710122e302790a05ae092c30d41d3553 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1134 | ||||
| 95385202 | MDExOlB1bGxSZXF1ZXN0OTUzODUyMDI= | 1136 | closed | 0 | WIP: remove some refs to xray | fmaussion 10050469 | There are some uses of xray that needed to be fixed. WIP: merge after you decide what to do with https://github.com/pydata/xarray/issues/1135 Also, I'd be in favor of removing the two notebooks in https://github.com/pydata/xarray/tree/master/examples since they are also available in the docs (http://xarray.pydata.org/en/latest/examples.html). The example on RTD have the disadvantage that it's less easy to do copy/paste with them, but notebooks are more error prone since they need to be maintained externally. | 2016-11-26T22:30:27Z | 2016-11-26T23:01:53Z | 2016-11-26T23:00:50Z | 2016-11-26T23:00:50Z | 1936ea39f22333bd5fd766d125429ba1cab37f1e | 0 | 2cd473b05e33858097a8a40fa7a947a7a82feb7e | b72d894154e182e90b56c76ac24d77d8f4a0677d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1136 | ||||
| 95400056 | MDExOlB1bGxSZXF1ZXN0OTU0MDAwNTY= | 1137 | closed | 0 | Pin package versions on RTD | fmaussion 10050469 | Now that we seem to have everything working on RTD, re-pin package versions (follow-up to https://github.com/pydata/xarray/pull/1101) | 2016-11-27T11:38:11Z | 2016-11-28T03:45:12Z | 2016-11-28T03:45:11Z | 2016-11-28T03:45:11Z | 3a2f06f961871b8a110d9c26521e9f10332259b9 | 0 | e0fe3f64193dadb9f9cc4ef679a9243928e09f37 | 1936ea39f22333bd5fd766d125429ba1cab37f1e | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1137 | ||||
| 95553209 | MDExOlB1bGxSZXF1ZXN0OTU1NTMyMDk= | 1139 | closed | 0 | Unpin python on RTD | fmaussion 10050469 | Pinning python to 3.5 introduced new [problems](https://readthedocs.org/projects/xray/builds/4723418/). Despite the default python being 3 [here](https://github.com/pydata/xarray/blob/master/readthedocs.yml#L4) and also in our RTD preferences (dashboard->advanced), RTD seems to still use py2 per default... Anyway, going back to py2 is the easiest for now, I might come back to this when I have more time. | 2016-11-28T18:35:51Z | 2016-11-28T22:13:58Z | 2016-11-28T20:00:17Z | 2016-11-28T20:00:17Z | bfff59a1c4c5795277abeb753e4c92cc891f8c08 | 0 | 0710df7b945519c9058c6850919502cbd811637c | 3a2f06f961871b8a110d9c26521e9f10332259b9 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1139 | ||||
| 95589089 | MDExOlB1bGxSZXF1ZXN0OTU1ODkwODk= | 1141 | closed | 0 | Try py3 again on RTD | fmaussion 10050469 | sorry about the many PRs :-( Let's see what happens with this one | 2016-11-28T22:27:33Z | 2016-11-28T23:38:59Z | 2016-11-28T23:38:59Z | 2016-11-28T23:38:59Z | f6577d6e609acd6814f2699e7a68ab3b00b97110 | 0 | a616d91bce636d59c2c7b751ea5a83bb64be9e7a | bfff59a1c4c5795277abeb753e4c92cc891f8c08 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1141 | ||||
| 95978225 | MDExOlB1bGxSZXF1ZXN0OTU5NzgyMjU= | 1144 | closed | 0 | Update ipython on RTD | fmaussion 10050469 | Another attempt to solve a cryptic error: https://readthedocs.org/projects/xray/builds/4727274/ But this time we are getting closer! I've found a report on ipython (https://github.com/ipython/ipython/issues/8850), an I've been able to reproduce it locally and solve it by updating to ipython 5 | 2016-11-30T21:33:55Z | 2016-11-30T22:56:24Z | 2016-11-30T22:45:41Z | 2016-11-30T22:45:41Z | b21948d7e89262042beb3a93df8e7afaf62695a4 | 0 | 4476c12b61aabf040fd997f959eded09c2acff64 | f6577d6e609acd6814f2699e7a68ab3b00b97110 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1144 | ||||
| 96956294 | MDExOlB1bGxSZXF1ZXN0OTY5NTYyOTQ= | 1155 | closed | 0 | RTD: fix savefig dir creation | fmaussion 10050469 | I've had a hard time finding out what was going on with missing RTD plots since we updated the packages until I came across this: https://github.com/ipython/ipython/issues/8733 The proposed fix creates the ``@savefig`` directory if not there. It works locally but I'm not sure if it will work on RTD (they might use a custom build directory). The other changes are minor tweaks to remove some build warnings and/or making use of the latest sphinx Makefile. I also removed a part of the conf.py which I think is not needed anymore. @shoyer do you remember what the ``inspect.findsource`` monkeypatch was good for? | 2016-12-07T16:21:01Z | 2016-12-07T16:53:07Z | 2016-12-07T16:38:03Z | 2016-12-07T16:38:03Z | 42133049b2a2240bd8c159f61a88157f42a78dc3 | 0 | e2c28c7d0ce7775a6e67acd36a8696bef2baf949 | c2717d13bcf4b2f6681e64b6d523cc3469fa7861 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1155 | ||||
| 96969622 | MDExOlB1bGxSZXF1ZXN0OTY5Njk2MjI= | 1156 | closed | 0 | RTD: furter attempt to fix savefig | fmaussion 10050469 | This implements a more robust solution based on the location of ``conf.py``... | 2016-12-07T17:26:07Z | 2016-12-07T17:30:18Z | 2016-12-07T17:30:18Z | 2016-12-07T17:30:18Z | 21b22808793cfd0905047d0384a26c13507db93b | 0 | 955e1138efc776726d9d9e889d85286e8ee9d624 | 42133049b2a2240bd8c159f61a88157f42a78dc3 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1156 | ||||
| 97112491 | MDExOlB1bGxSZXF1ZXN0OTcxMTI0OTE= | 1158 | closed | 0 | RTD: fix docs | fmaussion 10050469 | 2016-12-08T12:24:09Z | 2016-12-29T02:38:59Z | 2016-12-08T12:24:27Z | 2016-12-08T12:24:27Z | 8b54f939bc84b20ad4670f22375d2fd7c1761b7a | 0 | 03b7acddb81c0c40ca3c2711bec1b85d9b6f0d3e | 21b22808793cfd0905047d0384a26c13507db93b | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1158 | |||||
| 97163635 | MDExOlB1bGxSZXF1ZXN0OTcxNjM2MzU= | 1160 | closed | 0 | Norm should be passed to facetgrid too | fmaussion 10050469 | fixes https://github.com/pydata/xarray/issues/1159 | 2016-12-08T17:15:32Z | 2016-12-09T09:47:05Z | 2016-12-09T09:46:58Z | 2016-12-09T09:46:58Z | 2c7730d08a674ba6475acb596d4f12afb839f785 | 0 | d6f16e8caab4502ba5c6fdc19c14478e0b0246a5 | 8b54f939bc84b20ad4670f22375d2fd7c1761b7a | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1160 | ||||
| 98388171 | MDExOlB1bGxSZXF1ZXN0OTgzODgxNzE= | 1168 | closed | 0 | Add figsize, size, and aspect arguments to plotting methods | fmaussion 10050469 | Extends and finishes https://github.com/pydata/xarray/pull/637 I chose to keep seaborn's convention for two reasons: - it doesn't break existing code - now that ``figsize`` is also available, I expect the ``size`` and ``aspect`` kwargs to be less used in non-facetgrid plots Closes https://github.com/pydata/xarray/issues/897 | 2016-12-16T19:18:13Z | 2016-12-18T22:43:19Z | 2016-12-18T22:43:19Z | 2016-12-18T22:43:19Z | d31cb80fa7ca35437cde9a23a16935ea3bd6025d | 0 | fb28d5ebc842dd105aada2c1f21d2c1c0761f933 | 89a6732346542b234c0c655034c6e0ab49fecc56 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1168 | ||||
| 98409580 | MDExOlB1bGxSZXF1ZXN0OTg0MDk1ODA= | 1169 | closed | 0 | DOC: small improvements to the netCDF docs | fmaussion 10050469 | Partly addresses https://github.com/pydata/xarray/issues/768#issuecomment-187226020 and https://github.com/pydata/xarray/issues/1154, mostly by making the tone less defensive. I also added that we recommend the netCDF format for IO. (I think that the format is powerful enough for being useful in other disciplines than geosciences). I agree with @rabernat that the current page title (Serialization and IO) could be changed to something more accessible, but I don't know how. Two possibilities, both quite long (it looks a bit ugly on RTD): - "Reading and writing xarray data structures on disk" - "Reading/writing xarray data structures" | 2016-12-16T21:58:17Z | 2016-12-24T11:54:51Z | 2016-12-24T11:54:51Z | 2016-12-24T11:54:51Z | 88cc396f5117c09c76e15d6383aeca32b4d4a8bd | 0 | 32f95307a792a72cbb1d534542f906159f144e10 | 89a6732346542b234c0c655034c6e0ab49fecc56 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1169 | ||||
| 98475945 | MDExOlB1bGxSZXF1ZXN0OTg0NzU5NDU= | 1171 | closed | 0 | Fix tests for upcoming matplotlib v2 | fmaussion 10050469 | Just to see what happens with the upcoming matplotlib version 2 | 2016-12-18T14:20:19Z | 2017-01-04T07:43:04Z | 2017-01-04T07:43:04Z | 2017-01-04T07:43:04Z | 3001ee18462cdab5d367a8ecb3275774ca2ab89c | 0 | 17290d87d8b58d01c827bfe9da006b2259739fbd | 71d6a0e8bc89d7bbb4f89590139946e9fdf4f57d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1171 | ||||
| 99671769 | MDExOlB1bGxSZXF1ZXN0OTk2NzE3Njk= | 1191 | closed | 0 | Integer levels and vmin/vmax | fmaussion 10050469 | Follow-up to https://github.com/pydata/xarray/pull/1171#issuecomment-269556898 From the new docstring: ``` levels : int or list-like object, optional Split the colormap (cmap) into discrete color intervals. If an integer is provided, "nice" levels are chosen based on the data range: this can imply that the final number of levels is not exactly the expected one. Setting ``vmin`` and/or ``vmax`` with ``levels=N`` is equivalent to setting ``levels=np.linspace(vmin, vmax, N)``. ``` The logic overhead is quite simple, which is an argument in favor of this simple solution. It is consistent with mpl, as long as neither vmin or vmax are set. It _might_ change the outcome of some existing plots, though. Should I mention this in the "Breaking changes" section too? | 2016-12-29T16:10:22Z | 2017-01-03T09:50:14Z | 2017-01-03T09:50:14Z | 2017-01-03T09:50:14Z | 71d6a0e8bc89d7bbb4f89590139946e9fdf4f57d | 0 | dace3eb864d191ce08c4ed5fdf713d892006ea70 | feed9223129fbb87cadf698275088687755cc12d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1191 | ||||
| 101496450 | MDExOlB1bGxSZXF1ZXN0MTAxNDk2NDUw | 1206 | closed | 0 | RTD: fix facetted maps example | fmaussion 10050469 | follow-up to https://github.com/pydata/xarray/pull/1203 | 2017-01-13T18:48:08Z | 2017-01-14T09:15:54Z | 2017-01-14T09:15:54Z | 2017-01-14T09:15:54Z | 295e6514d945e8f362a41b4d991b7403739d12cc | 0 | e6770fd41c4b927a41c80ab9c7d1da5d283eb135 | 9a7e50279507dfa3023632b1a39116492a563698 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1206 | ||||
| 102283195 | MDExOlB1bGxSZXF1ZXN0MTAyMjgzMTk1 | 1220 | closed | 0 | Fix docs | fmaussion 10050469 | This PR fixes a problem we had with ipython on RTD: https://github.com/ipython/ipython/issues/8733 We this simple workaround we can now use the latest ipython version. Thanks to @takluyver for his help! | 2017-01-19T15:04:34Z | 2017-01-20T17:05:54Z | 2017-01-20T08:48:45Z | 2017-01-20T08:48:45Z | fec5bac40a6bdd377dd69b8dbbad91169be46839 | 0 | 8368f1ef17c06af5adbe7bf6e577bffd0a98fa61 | b44b37a5bd8fb613e6a7ce9c82c91e31b7ddf9bc | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1220 | ||||
| 102451217 | MDExOlB1bGxSZXF1ZXN0MTAyNDUxMjE3 | 1222 | closed | 0 | New testing module and tests refactor | fmaussion 10050469 | - [x] closes https://github.com/pydata/xarray/issues/1218 - [x] tests added / passed - [x] whatsnew entry | 2017-01-20T12:04:01Z | 2017-01-24T21:25:33Z | 2017-01-24T21:18:20Z | 2017-01-24T21:18:20Z | c800e48f0d22867e6c0ad714f61652c0e56e7cf2 | 0 | e5605c6de62a9025eb26ef4f2dd7d805368095c3 | 6d5ad44e4666a50ed91a201ce28ad0b4e3d727a4 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1222 | ||||
| 103023113 | MDExOlB1bGxSZXF1ZXN0MTAzMDIzMTEz | 1227 | closed | 0 | mpl v2 for the docs | fmaussion 10050469 | For some reason I can't reach the webpage but @shoyer seems to be able to do so: https://github.com/pydata/xarray/issues/1167#issuecomment-274966778 | 2017-01-24T23:04:55Z | 2017-01-25T00:00:55Z | 2017-01-25T00:00:55Z | 2017-01-25T00:00:55Z | 709ef84091a4acb7caddd43fd33511adcdfaf8ec | 0 | ef4fbbe472c35646c19c8e2829ffe21e69f7c9c5 | c800e48f0d22867e6c0ad714f61652c0e56e7cf2 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1227 | ||||
| 103666052 | MDExOlB1bGxSZXF1ZXN0MTAzNjY2MDUy | 1235 | closed | 0 | Use LooseVersion for bottleneck checks | fmaussion 10050469 | - [x] closes https://github.com/pydata/xarray/issues/1208 - [ ] tests added / passed - [x] passes ``git diff upstream/master | flake8 --diff`` - [ ] whatsnew entry | 2017-01-29T23:54:16Z | 2017-01-30T00:10:40Z | 2017-01-30T00:10:40Z | 2017-01-30T00:10:40Z | 384c9b3ebc5c25d111700bd2f8c998a557da888f | 0 | dadd37a508b5de1ac99e414faab2f6f7f7a4d427 | 6ccbdfd065e135bc58c409ff8fb6b2f4739fb4d5 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1235 | ||||
| 105704757 | MDExOlB1bGxSZXF1ZXN0MTA1NzA0NzU3 | 1260 | closed | 0 | Add RasterIO backend | fmaussion 10050469 | Follow-up to https://github.com/pydata/xarray/pull/1070 This is my first backend so this is going to be a bit more work than I expected, but with your help we should be able to get through this. A long todo list: - [x] closes https://github.com/pydata/xarray/issues/790 - [x] add tests - [x] passes ``git diff upstream/master | flake8 --diff`` - [x] whatsnew entry - [x] wrap __getitem__ for lazy data read - [x] ~~make coordinates variables lazy too~~ | 2017-02-10T20:59:31Z | 2017-06-06T16:44:43Z | 2017-06-06T10:25:22Z | 2017-06-06T10:25:22Z | 48c7164d38eaf20e166303df7cb8e7a61caa4e05 | 0 | d5c964e882e68470946eca9b97ac1908c7578e4b | c2588dadff82f2e56b9ec9c10d6d57661dbcce15 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1260 | ||||
| 109142875 | MDExOlB1bGxSZXF1ZXN0MTA5MTQyODc1 | 1296 | closed | 0 | Clearer terminology for coordinate variables | fmaussion 10050469 | - [x] closes https://github.com/pydata/xarray/issues/1295 | 2017-03-05T10:08:41Z | 2017-03-15T16:28:12Z | 2017-03-15T16:28:12Z | 2017-03-15T16:28:12Z | 57776ab6db0904f5240d89b1835df961b0fe0848 | 0 | 3bc8e05f239deab1163f92a9018810ae571f5f3b | 7f71e4087147938afa503e1460a05631f07c5c24 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1296 | ||||
| 116141874 | MDExOlB1bGxSZXF1ZXN0MTE2MTQxODc0 | 1377 | closed | 0 | Remove debug print() | fmaussion 10050469 | This was introduced by https://github.com/pydata/xarray/pull/1368 (@shoyer) | 2017-04-17T14:29:42Z | 2017-04-17T17:45:46Z | 2017-04-17T17:45:44Z | 2017-04-17T17:45:44Z | b6707198c413a6a25da2b778d31f1fb7d4d997b0 | 0 | 9bb7ea4368d03ef62c804ecfabf052861a4cee04 | 6753ec4acb40e9fe17b906e655c9ddb687bb7559 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1377 | ||||
| 119976298 | MDExOlB1bGxSZXF1ZXN0MTE5OTc2Mjk4 | 1402 | closed | 0 | Adds bottleneck to the test suite | fmaussion 10050469 | - [x] closes https://github.com/pydata/xarray/issues/1401 - [ ] tests added / passed - [ ] passes ``git diff upstream/master | flake8 --diff`` - [ ] whatsnew entry I don't know if we need to install all packages to cover all the tests which rely on bottleneck, but this was the easiest. | 2017-05-10T20:54:04Z | 2017-05-10T23:11:06Z | 2017-05-10T23:10:58Z | 2017-05-10T23:10:58Z | fd6e36e9869236ddf1862d4b5268ab2e07576e21 | 0 | 1ba2af963cd918bf79d28eb8a335f0375b616007 | e1982faf8e906ccdcb16b07462ffa77fd13bf69c | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1402 | ||||
| 120094098 | MDExOlB1bGxSZXF1ZXN0MTIwMDk0MDk4 | 1404 | closed | 0 | Fix pandas.tslib deprecation warning | fmaussion 10050469 | - [ ] closes #xxxx - [ ] tests added / passed - [ ] passes ``git diff upstream/master | flake8 --diff`` - [ ] whatsnew entry Since the last pandas update I get: ``` /home/mowglie/Documents/git/xarray/xarray/core/formatting.py:16: FutureWarning: The pandas.tslib module is deprecated and will be removed in a future version. from pandas.tslib import OutOfBoundsDatetime ``` | 2017-05-11T12:29:13Z | 2017-05-11T16:46:23Z | 2017-05-11T16:46:23Z | 2017-05-11T16:46:23Z | ba6351b14d6a6ba2d12b8ae8aacc9c4b76bdc003 | 0 | e20ca57b511c8e6931ca534a19990363b17ce614 | fd6e36e9869236ddf1862d4b5268ab2e07576e21 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1404 | ||||
| 121655717 | MDExOlB1bGxSZXF1ZXN0MTIxNjU1NzE3 | 1417 | closed | 0 | Update weather data example | fmaussion 10050469 | - [ ] Closes #xxxx - [ ] Tests added / passed - [ ] Passes ``git diff upstream/master | flake8 --diff`` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API For some reason a plot from the examples was rendered statically instead of live. This is now fixed, together with an update of pandas which prevents reshaping operations on indexes. Tested [here](http://xarray.pydata.org/en/fix-docs/examples/weather-data.html) | 2017-05-21T10:31:06Z | 2017-05-21T19:03:04Z | 2017-05-21T10:33:08Z | 2017-05-21T10:33:08Z | 5f92955f8f6e6378b690b922986de789985d2307 | 0 | 2b8077e48241fe7447ccb562407a4eb9ed159aa2 | d5c7e0612e8243c0a716460da0b74315f719f2df | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1417 | ||||
| 121659964 | MDExOlB1bGxSZXF1ZXN0MTIxNjU5OTY0 | 1419 | closed | 0 | Add sphinx-gallery to the docs | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/1061 - [ ] Tests added / passed - [ ] Passes ``git diff upstream/master | flake8 --diff`` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API This uses [sphinx-gallery](http://sphinx-gallery.readthedocs.io) to illustrate some examples of the xarray workflow. See it rendered [here](http://xarray.pydata.org/en/fix-docs/auto_gallery/index.html) It's nicer for the gallery if there is a plot to draw in the end but it doesn't *have* to be a plot. Once the gallery gets more examples it's possible to sort them by topic (see the sphinx gallery documentation for an overview of the possibilities). I could think of several other things we could add (including moving or copying @jhamman and @rabernat 's examples to the gallery), but I thought it's better to merge quickly in order to encourage the community to contribute with more examples before the next release. | 2017-05-21T13:00:44Z | 2017-05-24T15:20:41Z | 2017-05-24T15:20:41Z | 2017-05-24T15:20:40Z | f7eb309368a75f5010261c23b95eaa9625d7353a | 0 | cc687da609b864737f0da295c3592ac3b1e852f2 | 3737d2610bb6466babc5fe623eb8444d44dc0ceb | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1419 | ||||
| 123027910 | MDExOlB1bGxSZXF1ZXN0MTIzMDI3OTEw | 1432 | closed | 0 | Add dask specific kwargs to DataArray.chunk() | fmaussion 10050469 | - [ ] Closes #xxxx - [ ] Tests added / passed - [x] Passes ``git diff upstream/master | flake8 --diff`` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API this is needed for the Rasterio PR (https://github.com/pydata/xarray/pull/1260#discussion_r118824181) There was no test for these functionalities in the xarray test suite for ``Dataset`` either, so I just added a dummy test for one of the keywords. | 2017-05-30T11:30:27Z | 2017-05-30T18:04:02Z | 2017-05-30T16:50:02Z | 2017-05-30T16:50:02Z | 8df660b37692e42965a672563941d85ed6d55229 | 0 | a5335f2336dd5dbce0d235fdb7e1f1c50e24699f | 9287caa70ea69d4afe07f111fed2b99f795f069d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1432 | ||||
| 124159334 | MDExOlB1bGxSZXF1ZXN0MTI0MTU5MzM0 | 1443 | closed | 0 | DOC: add salem to the list of projects extending xarray | fmaussion 10050469 | [Salem](https://github.com/fmaussion/salem) is likely to remain a small project but it has a more-than-one user base and might provide some inspiration for the future [pangeo](https://pangeo-data.github.io) projects. | 2017-06-06T10:37:50Z | 2017-06-07T11:59:52Z | 2017-06-07T11:57:35Z | 2017-06-07T11:57:35Z | 33bc77074a063eecbc066989051998f84db111b0 | 0 | c7a20dcbb005b4d88d67aec607d76d754d071685 | 48c7164d38eaf20e166303df7cb8e7a61caa4e05 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1443 | ||||
| 124444851 | MDExOlB1bGxSZXF1ZXN0MTI0NDQ0ODUx | 1445 | closed | 0 | DOC: add rasterio to build environment | fmaussion 10050469 | This is needed for the doc recipe to run | 2017-06-07T15:08:05Z | 2017-06-07T15:11:08Z | 2017-06-07T15:11:07Z | 2017-06-07T15:11:07Z | e39dae4c4ba83de09bea16ed5b3132ce4e88ba98 | 0 | 75f39b96a5cae28da7caa0aae9891cdb0140d402 | 33bc77074a063eecbc066989051998f84db111b0 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1445 | ||||
| 134326508 | MDExOlB1bGxSZXF1ZXN0MTM0MzI2NTA4 | 1502 | closed | 0 | Fix rasterio builds in docs | fmaussion 10050469 | - [ ] Closes #xxxx - [ ] Tests added / passed - [ ] Passes ``git diff upstream/master | flake8 --diff`` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API The pinned version of rasterio we use for the doc builds isn't available anymore: https://github.com/conda-forge/rasterio-feedstock/pull/36 Tests: - builds: https://readthedocs.org/projects/xray/builds/5796746/ - displays correctly: http://xarray.pydata.org/en/fix-docs/auto_gallery/plot_rasterio.html#sphx-glr-auto-gallery-plot-rasterio-py | 2017-08-06T13:30:39Z | 2017-08-07T09:21:39Z | 2017-08-07T09:21:39Z | 2017-08-07T09:21:39Z | 4ebc8ab4d79219f8120dbc501eca75d16f9df471 | 0 | 80ba78628a4decbe2630b77e2926784f73f8d09b | e3e6db5b1bf94fd78c5a1b9d872ea8dcb91a7b9c | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1502 | ||||
| 152125692 | MDExOlB1bGxSZXF1ZXN0MTUyMTI1Njky | 1712 | closed | 0 | Use rasterio's transform instead of homemade coordinates | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/1686 - [x] Tests added / passed - [x] Passes ``git diff upstream/master **/*py | flake8 --diff`` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2017-11-12T21:52:04Z | 2018-01-26T13:51:15Z | 2018-01-26T13:50:54Z | 2018-01-26T13:50:54Z | 015daca45bd7be32377bdf429c02117d5955452c | 0 | 21957aaec977f9d222441d0d33ddc2075225167a | 009291139fde0c859ee565141cdb3b6a3d28cba0 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1712 | ||||
| 160925414 | MDExOlB1bGxSZXF1ZXN0MTYwOTI1NDE0 | 1808 | closed | 0 | Add gallery example for multiple lines plot | fmaussion 10050469 | Extends https://github.com/pydata/xarray/pull/1804 by adding some usage examples to the gallery. Here is how the plot looks like:  cc @dcherian and @shoyer | 2018-01-03T14:45:48Z | 2018-01-03T18:34:40Z | 2018-01-03T18:34:40Z | 2018-01-03T18:34:40Z | 5a28b89d8f32a16d8529d6514c04992b5ee7a349 | 0 | 613a64e201e990d84a4a1793f2a01dcaf85b7c01 | 30c849eed36f313db90a0f2e3eb8a135991240f6 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1808 | ||||
| 166787888 | MDExOlB1bGxSZXF1ZXN0MTY2Nzg3ODg4 | 1881 | closed | 0 | Fix rasterio example in docs | fmaussion 10050469 | https://github.com/pydata/xarray/pull/1796 introduced a bug in the doc gallery. This PR reverts the code to the previous greyscale example and adds a new case using imshow (the use case is different, as I tried to explain in the descriptions). I also took care of https://github.com/pydata/xarray/issues/1789#issuecomment-356068358 : the docs should now build even when rasterio is not installed. cc @Zac-HD , @shoyer | 2018-02-02T12:13:33Z | 2018-02-02T19:11:01Z | 2018-02-02T19:10:54Z | 2018-02-02T19:10:54Z | e9b98d032adf75509c430056c086389f5f3134fc | 0 | edca54dc9566dd45b27b42a9591eb8c79e741340 | becd77c44d9436a142db4a98de2b30d388ee6d2b | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1881 | ||||
| 167427609 | MDExOlB1bGxSZXF1ZXN0MTY3NDI3NjA5 | 1890 | closed | 0 | Simplify some rasterio tests | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/1843 - [x] Tests added - [x] Tests passed - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API This PR restores the tests that were incorrectly removed in https://github.com/pydata/xarray/pull/1817 and adds the what's new entry I forgot in https://github.com/pydata/xarray/pull/1712 | 2018-02-06T14:24:34Z | 2018-02-07T08:40:34Z | 2018-02-07T08:40:34Z | 2018-02-07T08:40:34Z | 1d3239982db9778e89a48fe55b01d0a525673a7a | 0 | b92e516d4611aef6928173b2e485290a99d191ce | 7357a07806d2493c7cb2765f01d54ec9a8f2c87d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1890 | ||||
| 167428781 | MDExOlB1bGxSZXF1ZXN0MTY3NDI4Nzgx | 1891 | closed | 0 | Use pip install -e in contributing docs | fmaussion 10050469 | I think that pip install is the recommended way to install packages in dev mode (see also http://www.python3statement.org/practicalities/ ) | 2018-02-06T14:28:52Z | 2018-02-06T19:59:04Z | 2018-02-06T19:59:04Z | 2018-02-06T19:59:04Z | 518436576b1661bb04e95987abf7678749b3d634 | 0 | ffba12fecd8ecc8f50a0717c19cfd0a7ef2d3c72 | 7357a07806d2493c7cb2765f01d54ec9a8f2c87d | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1891 | ||||
| 168415605 | MDExOlB1bGxSZXF1ZXN0MTY4NDE1NjA1 | 1902 | closed | 0 | _color_palette consistent with or without seaborn | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/1896 - [ ] Tests added - [ ] Tests passed - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API Instead of relying on seaborn per default we now use mpl and fall back to seaborn if cmap is not recognized (e.g. with `cmap="husl"`). | 2018-02-10T19:00:59Z | 2018-02-16T21:08:32Z | 2018-02-16T21:08:32Z | 2018-02-16T21:08:32Z | 8c5c549e842644b3b5acabf40a98d7fe7e33ad89 | 0 | f8917f354361166c3dd68207affa43be9b9223ba | d191352b6c1e15a2b6105b4b76552fe974231396 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1902 | ||||
| 172675782 | MDExOlB1bGxSZXF1ZXN0MTcyNjc1Nzgy | 1958 | closed | 0 | Update some packages on RTD | fmaussion 10050469 | See https://github.com/pydata/xarray/pull/1957 | 2018-03-03T16:41:00Z | 2018-03-03T16:41:10Z | 2018-03-03T16:41:10Z | 2018-03-03T16:41:10Z | a32475bb21b0efd83c30f36e41346c00f77f4b52 | 0 | 3a754a3ed1e39682bbca31459de71343ebb25264 | 350e97793f89ddd4097b97e0c4af735a5144be24 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/1958 | ||||
| 177249971 | MDExOlB1bGxSZXF1ZXN0MTc3MjQ5OTcx | 2015 | closed | 0 | Fix an overflow bug in decode_cf_datetime | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2002 - [x] Tests added - [x] Tests passed - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API Not sure yet if this is the best way to do this. | 2018-03-24T17:54:36Z | 2018-03-31T01:16:15Z | 2018-03-31T01:16:14Z | 2018-03-31T01:16:14Z | c78469a63417d9b7da0d5662788f10fb82923ea3 | 0 | 8283967ec13d5d7780806c00ee49d14aeb756973 | 7c2c43ce6b1792e1193635ab9b64fd248266f632 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2015 | ||||
| 184908816 | MDExOlB1bGxSZXF1ZXN0MTg0OTA4ODE2 | 2091 | closed | 0 | DOC: uniformize variable names in indexing.rst | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2088 https://github.com/pydata/xarray/commit/6402391cf206fd04c12d44773fecd9b42ea0c246 overwrote an array which was needed later on. In general the whole page was a bit messy with the same initial array being forgotten and then re-used much later. This PR attempts to uniformize the variable names in order to make self-consistent subsection examples. I hope I didn't brake something on the way, but it looks ok on my local build. (also renamed a gallery example plot which wasn't showing up correctly) | 2018-04-30T09:11:14Z | 2018-04-30T17:17:53Z | 2018-04-30T17:17:53Z | 2018-04-30T17:17:52Z | d1e1440dc5d0bc9c341da20fde85b56f2a3c1b5b | 0 | a5d767136ca609581f4b121ea263108bae1e661e | c42cbe787d530db48575d73fe7a3910b0a0e4fd8 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2091 | ||||
| 188676780 | MDExOlB1bGxSZXF1ZXN0MTg4Njc2Nzgw | 2146 | closed | 0 | Add favicon to docs? | fmaussion 10050469 | Don't know if we want this, but it's possible to replace the default RTD icon. I'm not even sure if the cool kids are using bookmarks anymore, but I still do. This is how it looks like on my Firefox fav tab:  | 2018-05-17T09:35:21Z | 2018-05-19T20:37:18Z | 2018-05-17T16:55:31Z | 2018-05-17T16:55:31Z | 7bab27cc637a60bff2b510d4f4a419c9754eeaa3 | 0 | 27c07bfed9c9083de0c5c663bc0d075768315149 | 008c2c8e7544b0d8ea4e2fecde5625afabe6ea63 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2146 | ||||
| 198469230 | MDExOlB1bGxSZXF1ZXN0MTk4NDY5MjMw | 2260 | closed | 0 | Plotting: do not check for monotonicity with 2D coords | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2250 - [x] Tests added - [x] Tests passed - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API | 2018-06-30T09:47:20Z | 2018-07-03T09:17:02Z | 2018-07-03T09:16:27Z | 2018-07-03T09:16:27Z | 5ddfb6dc07f9de08bf95232df4a35e95a85fd113 | 0 | e4a66115f70999be9de6844bcea6e5fc20a65ca7 | 04a78d50a928f4af2efc4e1d19370c76d822dbb6 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2260 | ||||
| 202966281 | MDExOlB1bGxSZXF1ZXN0MjAyOTY2Mjgx | 2303 | closed | 0 | Rename "Recipes" to "Gallery" | fmaussion 10050469 | Simply because it makes more sense after all. The link address won't change so it's not a biggie (http://xarray.pydata.org/en/latest/auto_gallery/index.html) | 2018-07-20T22:03:27Z | 2018-07-23T16:33:08Z | 2018-07-23T16:33:08Z | 2018-07-23T16:33:08Z | 46732461d01fc1a2dd097599bb384b7306f1c0a5 | 0 | 9d964a0ab68cfa0689901842b204b20395570f03 | b8a342ae845a7d734d391c4b597ee689ed9c6a72 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2303 | ||||
| 203572590 | MDExOlB1bGxSZXF1ZXN0MjAzNTcyNTkw | 2310 | closed | 0 | Make RTD builds faster | fmaussion 10050469 | See https://github.com/pydata/xarray/issues/2306 This makes the builds a little bit faster. But we are still very close to the 900 s limit. I tried to pin more packages this morning but this didn't work out. I'll merge this first (the latest build worked with this config, https://readthedocs.org/projects/xray/builds/) and try again at a later stage. | 2018-07-24T15:45:17Z | 2018-07-27T08:20:43Z | 2018-07-27T08:20:43Z | 2018-07-27T08:20:43Z | 9802d618251eae88474f680999db4c23967c8f7a | 0 | 28db89632475175ed90cec9e51394756ea338c9e | 46732461d01fc1a2dd097599bb384b7306f1c0a5 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2310 | ||||
| 204172929 | MDExOlB1bGxSZXF1ZXN0MjA0MTcyOTI5 | 2317 | closed | 0 | Remove test on rasterio rc and test for 0.36 instead | fmaussion 10050469 | See https://github.com/pydata/xarray/issues/2316 | 2018-07-26T15:03:20Z | 2018-07-30T11:05:37Z | 2018-07-30T11:05:30Z | 2018-07-30T11:05:30Z | 5d8670f6949fed60ab570075ae7dc67200f9ff51 | 0 | 78e760c9c60a55798e885db1112ab738cfad4e0c | ded0a684136540962bcc409e6272b1cebb5af30a | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2317 | ||||
| 216948981 | MDExOlB1bGxSZXF1ZXN0MjE2OTQ4OTgx | 2425 | closed | 0 | Plotting: restore xyincrease kwarg default to True | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2422 - [x] Tests added - [x] Tests passed - [x] Fully documented, including `whats-new.rst` https://github.com/pydata/xarray/pull/2294 introduced the new ``xincrease`` and ``yincrease`` kwargs and a behavior documented as: ``` xincrease : None, True, or False, optional Should the values on the x axes be increasing from left to right? if None, use the default for the matplotlib function. ``` The default was ``None``, I suggest to set it to ``True``: it was the default before https://github.com/pydata/xarray/pull/2294 and I think it is what most users expect. | 2018-09-20T12:12:48Z | 2018-09-21T17:36:23Z | 2018-09-21T17:36:21Z | 2018-09-21T17:36:21Z | c1c576f75a2c4c2f8fad314c10588f45c5a5c573 | 0 | 5fdebb4e82c71aa882ace74d97caf100f0f37511 | 5b87b6e2f159b827f739e12d4faae57a0b6f6178 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2425 | ||||
| 224475809 | MDExOlB1bGxSZXF1ZXN0MjI0NDc1ODA5 | 2498 | closed | 0 | Small fix in rasterio docs | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2497 | 2018-10-20T13:48:51Z | 2018-10-22T00:01:09Z | 2018-10-22T00:01:07Z | 2018-10-22T00:01:05Z | dffbcb8b7a6745ddbb061d554c0475afb9122bf3 | 0 | 9c8a265331516725dd214229c4fa89476ce2e170 | 9f4474d657193f1c7c9aac25bb2edf94755a8593 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2498 | ||||
| 229882465 | MDExOlB1bGxSZXF1ZXN0MjI5ODgyNDY1 | 2552 | closed | 0 | Attempt to reproduce HDF error | fmaussion 10050469 | This is just a test to see if I can reproduce an HDF error reported in https://github.com/pydata/xarray/issues/2551 | 2018-11-10T10:22:47Z | 2018-11-11T12:10:46Z | 2018-11-11T12:10:46Z | c6d32bd9b9ccea2c67ba661b585e00e65e1aa03d | 0 | de9c9a53d87b08cc924bf15517e448c2216b29b3 | 575e97aef405c9b473508f5bc0e66332df4930f3 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2552 | |||||
| 233328978 | MDExOlB1bGxSZXF1ZXN0MjMzMzI4OTc4 | 2571 | closed | 0 | CF: also decode time bounds when available | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/2565 - [x] Tests added - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API Not sure if this is the best way to handle it, but it seems to work | 2018-11-24T16:50:13Z | 2018-12-19T17:19:05Z | 2018-12-19T17:19:05Z | 2018-12-19T17:19:04Z | 57348abb1f4d00a3015d0e7f7a5f0df3c6b59481 | 0 | 0998d2b8a5e325b0d3061a8c72cadcd6b14376bb | f8cced75f718ca0ad278224cf4b09bd42f5cd999 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2571 | ||||
| 264131557 | MDExOlB1bGxSZXF1ZXN0MjY0MTMxNTU3 | 2850 | closed | 0 | More informative error when writing attrs to netCDF | fmaussion 10050469 | Closes #3080 Some attribute names aren't valid netCDF4 keys. For example: ```python import xarray as xr ds = xr.Dataset({'x': ('y', [1, 2, 3], {'CLASS': 'foo'})}) ds.to_netcdf('test.nc') ``` will fail with: ```NetCDF: String match to name in use``` This is hard to debug if you don't know which attribute is faulty. With this small change the error should be more informative: ```AttributeError: The following exception occurred when attempting to set attribute (CLASS, foo): "NetCDF: String match to name in use"``` | 2019-03-25T13:58:30Z | 2022-05-03T16:16:21Z | 2022-05-03T16:16:21Z | 1f9d9b64828e32a9950e3daf7c8563c251511c08 | 0 | a50581ac193e530382c6720889aa5763e44e8772 | 7bf9df9d75c40bcbf2dd28c47204529a76561a3f | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/2850 | |||||
| 778907708 | PR_kwDOAMm_X84ubTA8 | 5978 | closed | 0 | Add "see also" in to_dataframe docs | fmaussion 10050469 | A very modest contribution... I miss contributing to xarray! Believe it or not, I did not know about `to_pandas` until today... | 2021-11-11T21:15:15Z | 2021-11-13T17:35:43Z | 2021-11-13T17:35:43Z | 2021-11-13T17:35:43Z | 5e2f1dcf103da2b2b047b9d136c194a2e9a2e4f3 | 0 | 9299ca2dfbc7eec71532191e463e8fff5669798a | 5871637873cd83c3a656ee6f4df86ea6628cf68a | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/5978 | ||||
| 779238754 | PR_kwDOAMm_X84ucj1i | 5981 | closed | 0 | Allow string formatting of scalar DataArrays | fmaussion 10050469 | - [x] Closes https://github.com/pydata/xarray/issues/5976 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` This is a first try at formatting dataarray scalars. Here is the current behavior: ```python In [1]: import xarray as xr ...: import numpy as np In [2]: a = np.array(1) ...: da = xr.DataArray(a) In [3]: print(a) 1 In [4]: print(da) <xarray.DataArray ()> array(1) In [5]: print('{}'.format(a)) 1 In [6]: print('{}'.format(da)) <xarray.DataArray ()> array(1) In [7]: print('{:.3f}'.format(a)) 1.000 In [8]: print('{:.3f}'.format(da)) 1.000 In [9]: a = np.array([1, 2]) ...: da = xr.DataArray(a) In [10]: print('{}'.format(a)) [1 2] In [11]: print('{}'.format(da)) <xarray.DataArray (dim_0: 2)> array([1, 2]) Dimensions without coordinates: dim_0 In [12]: print('{:.3f}'.format(a)) --------------------------------------------------------------------------- TypeError Traceback (most recent call last) <ipython-input-12-c5afc7863e89> in <module> ----> 1 print('{:.3f}'.format(a)) TypeError: unsupported format string passed to numpy.ndarray.__format__ In [13]: print('{:.3f}'.format(da)) --------------------------------------------------------------------------- TypeError Traceback (most recent call last) <ipython-input-13-bddebd8462bd> in <module> ----> 1 print('{:.3f}'.format(da)) ~/disk/Dropbox/HomeDocs/git/xarray/xarray/core/common.py in __format__(self, format_spec) 162 return formatting.array_repr(self) 163 # Else why fall back to numpy --> 164 return self.values.__format__(format_spec) 165 166 def _iter(self: Any) -> Iterator[Any]: TypeError: unsupported format string passed to numpy.ndarray.__format__ ``` I don't think there is any backwards compatibility issue but lets see if the tests pass | 2021-11-12T09:44:43Z | 2022-05-09T15:25:25Z | 2022-05-09T15:25:02Z | 2022-05-09T15:25:02Z | bbb14a5d8383520f1a1e7e6d885c03ecddfbcf47 | 0 | 34a38b1657599ad2a7c406f6746e754e989ca4f5 | 126051f2bf2ddb7926a7da11b047b852d5ca6b87 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/5981 | ||||
| 926778953 | PR_kwDOAMm_X843PYZJ | 6569 | closed | 0 | Add some warnings about rechunking to the docs | fmaussion 10050469 | <!-- Feel free to remove check-list items aren't relevant to your change --> This adds some warnings at the right places when rechunking a dataset opened with `open_mfdataset` (see https://github.com/pangeo-data/rechunker/issues/100#issuecomment-1116189019 for context) Thanks to @dcherian for the wisdom of the day! | 2022-05-03T16:48:02Z | 2022-05-10T05:54:13Z | 2022-05-10T05:54:05Z | 2022-05-10T05:54:05Z | 218e77a9f2f6af0fc2a944563eb0ba2e8f457051 | 0 | 5fca7b0149753b801ee2e5668e0aa791e7cd67c8 | 126051f2bf2ddb7926a7da11b047b852d5ca6b87 | MEMBER | xarray 13221727 | https://github.com/pydata/xarray/pull/6569 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [pull_requests] (
[id] INTEGER PRIMARY KEY,
[node_id] TEXT,
[number] INTEGER,
[state] TEXT,
[locked] INTEGER,
[title] TEXT,
[user] INTEGER REFERENCES [users]([id]),
[body] TEXT,
[created_at] TEXT,
[updated_at] TEXT,
[closed_at] TEXT,
[merged_at] TEXT,
[merge_commit_sha] TEXT,
[assignee] INTEGER REFERENCES [users]([id]),
[milestone] INTEGER REFERENCES [milestones]([id]),
[draft] INTEGER,
[head] TEXT,
[base] TEXT,
[author_association] TEXT,
[auto_merge] TEXT,
[repo] INTEGER REFERENCES [repos]([id]),
[url] TEXT,
[merged_by] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_pull_requests_merged_by]
ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
ON [pull_requests] ([user]);