issues
13 rows where user = 15079414 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: comments, created_at (date), updated_at (date), closed_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1386771423 | I_kwDOAMm_X85SqHPf | 7091 | Reshaping doc intro looks incomplete | zmoon 15079414 | closed | 0 | 3 | 2022-09-26T21:52:21Z | 2023-03-31T15:23:32Z | 2023-03-31T15:23:32Z | CONTRIBUTOR | Even though it is a complete sentence, it is missing a period, and probably should be expanded. Or just removed if it's not going to say anything beyond the title ("Reshaping and reorganizing data"). |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/7091/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
627805952 | MDU6SXNzdWU2Mjc4MDU5NTI= | 4114 | Optionally create new figure automatically | zmoon 15079414 | closed | 0 | 5 | 2020-05-30T19:51:36Z | 2023-03-12T21:20:35Z | 2023-03-12T21:20:35Z | CONTRIBUTOR | Feature requestI think it would be nice to be able to configure (as a runtime option or somesuch) the behavior of the plotting methods if an Or, is there an easy way to runtime patch |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/4114/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
1436755752 | I_kwDOAMm_X85Voyco | 7258 | mypy complaint about `.to_netcdf` `encoding` | zmoon 15079414 | closed | 0 | 6 | 2022-11-05T00:57:26Z | 2022-11-11T16:43:46Z | 2022-11-11T10:37:55Z | CONTRIBUTOR | What happened?
I am using something like
What did you expect to happen?No response Minimal Complete Verifiable ExampleNo response MVCE confirmation
Relevant log outputNo response Anything else we need to know?No response Environmentmypy 0.982, xarray 2022.10.0
INSTALLED VERSIONS
------------------
commit: None
python: 3.9.13 | packaged by conda-forge | (main, May 27 2022, 16:50:36) [MSC v.1929 64 bit (AMD64)]
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
LOCALE: ('English_United States', '1252')
libhdf5: 1.12.1
libnetcdf: 4.8.1
xarray: 2022.10.0
pandas: 1.5.1
numpy: 1.23.4
scipy: 1.9.3
netCDF4: 1.6.0
pydap: None
h5netcdf: None
h5py: None
Nio: None
zarr: None
cftime: 1.6.1
nc_time_axis: None
PseudoNetCDF: None
rasterio: 1.3.2
cfgrib: None
iris: None
bottleneck: None
dask: 2022.8.1
distributed: None
matplotlib: 3.6.1
cartopy: 0.21.0
seaborn: 0.11.2
numbagg: None
fsspec: 2022.7.1
cupy: None
pint: None
sparse: None
flox: None
numpy_groupies: None
setuptools: 65.2.0
pip: 22.3
conda: None
pytest: 7.2.0
IPython: 8.4.0
sphinx: 4.5.0
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/7258/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
1372114101 | PR_kwDOAMm_X84-5kwS | 7033 | Update merge docstrings | zmoon 15079414 | closed | 0 | 2 | 2022-09-13T23:23:58Z | 2022-09-22T22:17:51Z | 2022-09-22T20:14:15Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/7033 |
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/7033/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
1344847532 | I_kwDOAMm_X85QKL6s | 6935 | `compat='override'` not documented for `Dataset.merge()` | zmoon 15079414 | closed | 0 | 1 | 2022-08-19T19:59:57Z | 2022-09-22T20:14:16Z | 2022-09-22T20:14:16Z | CONTRIBUTOR | It does accept it. Should be documented here: Can just be taken from |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6935/reactions", "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
1343642737 | I_kwDOAMm_X85QFlxx | 6931 | `.swap_dims()` can modify original object | zmoon 15079414 | closed | 0 | 0 | 2022-08-18T21:01:27Z | 2022-08-22T10:39:54Z | 2022-08-22T10:39:54Z | CONTRIBUTOR | What happened?This is kind of a convoluted example, but something I ran into. It appears that in certain cases What did you expect to happen?I expected it not to modify the original object. Minimal Complete Verifiable Example```Python import numpy as np import xarray as xr nz = 11 ds = xr.Dataset( data_vars={ "y": ("z", np.random.rand(nz)), "lev": ("z", np.arange(nz) * 10), # ^ We want this to be a dimension coordinate }, ) print(f"ds\n{ds}") print(f"\nds, 'lev' -> dim coord\n{ds.swap_dims(z='lev')}") ds2 = ( ds.swap_dims(z="lev") .rename_dims(lev="z") .reset_index("lev") .reset_coords() ) print(f"\nds2\n{ds2}") ^ This Dataset appears same as the originalprint(f"\nds2, 'lev' -> dim coord\n{ds2.swap_dims(z='lev')}") ^ Produces a Dataset with dimension coordinate 'lev'print(f"\nds2 after .swap_dims() applied\n{ds2}") ^
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6931/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
1343663760 | I_kwDOAMm_X85QFq6Q | 6932 | Italic not working in top of Terminology page | zmoon 15079414 | closed | 0 | 1 | 2022-08-18T21:25:04Z | 2022-08-20T07:30:41Z | 2022-08-20T07:30:41Z | CONTRIBUTOR | What happened?Looks like the intention is for the text to be all italic, but where the source breaks it is not working. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6932/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
1223227817 | I_kwDOAMm_X85I6Pmp | 6565 | `DataArray.nbytes` listed twice in API doc block | zmoon 15079414 | closed | 0 | 3 | 2022-05-02T18:54:11Z | 2022-07-22T17:25:33Z | 2022-07-22T17:25:33Z | CONTRIBUTOR | { "url": "https://api.github.com/repos/pydata/xarray/issues/6565/reactions", "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | |||||||
1076378062 | I_kwDOAMm_X85AKDnO | 6063 | <https://xarray.pydata.org> redirects to <http://xarray.pydata.org/en/stable/> | zmoon 15079414 | closed | 0 | 5 | 2021-12-10T03:14:37Z | 2021-12-11T15:23:39Z | 2021-12-11T15:23:39Z | CONTRIBUTOR | (https -> http), which seems not ideal |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/6063/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
991477547 | MDExOlB1bGxSZXF1ZXN0NzI5OTM0NzQ0 | 5780 | "Xarray" and "xarray" | zmoon 15079414 | closed | 0 | 2 | 2021-09-08T19:55:57Z | 2021-09-08T21:06:25Z | 2021-09-08T20:39:04Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/5780 | Updating readme and user-facing docs according to https://github.com/pydata/xarray/issues/1306 (final comment)
Notes: * I didn't yet change the contributing page, since it seems to have its own convention (though not used everywhere): xarray (bold and lowercase). * I mostly didn't touch internal docs pages / docstrings. * Also modified some cases of NumPy, pandas, and Dask according to their conventions, but could do more there, especially with NumPy. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5780/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
894819396 | MDU6SXNzdWU4OTQ4MTkzOTY= | 5337 | `colors` in Dataset plot methods | zmoon 15079414 | open | 0 | 2 | 2021-05-18T22:01:48Z | 2021-07-04T01:12:45Z | CONTRIBUTOR | While working on the plot method docstrings (#5285), I (and @keewis) found that the For My original notes on
Yeah, it seems like the `colors` argument is not used in `ds.plot.scatter`. But no error is raised, `colors` is just silently dropped (`ax.scatter` would raise `AttributeError` if it weren't) in most cases. I did find that you can get the marker colors to change by passing `color` or `c` with a discrete `hue_style`.
```python
import xarray as xr
import numpy as np
ds = xr.tutorial.scatter_example_dataset()
ds["c"] = (ds.A.dims, np.random.choice(("r", "g", "b"), ds.A.shape))
ds.plot.scatter("A", "B", hue="c", c=(0, 0, 0)) # works but prints (doesn't raise) warning
ds.plot.scatter("A", "B", hue="c", color=(0, 0, 0)) # works
```
However, if you have a continuous `hue_style`, passing `c` is ignored (since this is done internally), and passing `color` raises `ValueError` since it conflicts with `c`.
It seems like at the moment, `colors` is really only intended to be used with contour(f) for levels, like how it is in Matplotlib. Maybe in the future it could be used to allow passing colors to be used in the color cycle for discrete `hue_style`, but it doesn't currently do that. So for now, maybe in the docstring we should note this current behavior (doing nothing or raising error).
~~`levels` is also unused in `_dsplot` functions, maybe could be removed~~ actually I was able to get `colors` to sort of work with discrete `hue_style` by also providing `levels`, but `levels` only makes sense for numeric type:
```python
ds["c2"] = (ds.A.dims, np.random.choice((1, 2, 3), ds.A.shape))
ds.plot.scatter("A", "B", hue="c2", colors=["r", "g", "b"], levels=[1, 2, 3, 4]) # works (rgb)
ds.plot.scatter("A", "B", hue="c2", hue_style="discrete", colors=["r", "g", "b"]) # `colors` does nothing
```
_Originally posted by @zmoon in https://github.com/pydata/xarray/pull/5285#discussion_r632986368_
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5337/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue | ||||||||
883153591 | MDExOlB1bGxSZXF1ZXN0NjM2NjQ3NzQw | 5285 | Clean up and enhance plot method docstrings | zmoon 15079414 | closed | 0 | 6 | 2021-05-10T01:49:30Z | 2021-05-18T15:25:43Z | 2021-05-18T15:25:43Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/5285 |
Summary:
* use code-literal style for variables (arguments) and other Python identifiers
* fix some type specifications
* add more references where helpful
* italic for x and y when talking about axes, like in math
* correct a bit of grammar stuff
* tell which Matplotlib function is being wrapped at the top
* capitalize Matplotlib when referring to the library in general, since that is how they do it in their docs, like xarray is lowercase unless starting the sentence
* ~~remove |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5285/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
890235341 | MDExOlB1bGxSZXF1ZXN0NjQzMjg3MTM3 | 5293 | FacetGrid docstrings | zmoon 15079414 | closed | 0 | 3 | 2021-05-12T15:51:03Z | 2021-05-13T16:57:42Z | 2021-05-13T16:36:17Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/5293 |
Summary:
* Add |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5293/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);