issue_comments
25 rows where user = 1964655 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- ghisvail · 25 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
362793230 | https://github.com/pydata/xarray/issues/1879#issuecomment-362793230 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2Mjc5MzIzMA== | ghisvail 1964655 | 2018-02-03T09:24:19Z | 2018-02-03T09:24:19Z | CONTRIBUTOR |
Correct.
That's already the case, see: https://packages.debian.org/source/sid/rasterio What about |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
362712709 | https://github.com/pydata/xarray/issues/1879#issuecomment-362712709 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2MjcxMjcwOQ== | ghisvail 1964655 | 2018-02-02T21:27:40Z | 2018-02-02T21:27:40Z | CONTRIBUTOR | Well, I am considering (perhaps wrongly) what's in Back to the original topic, should |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
362709426 | https://github.com/pydata/xarray/issues/1879#issuecomment-362709426 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2MjcwOTQyNg== | ghisvail 1964655 | 2018-02-02T21:14:13Z | 2018-02-02T21:14:13Z | CONTRIBUTOR | And |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
362708442 | https://github.com/pydata/xarray/issues/1879#issuecomment-362708442 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2MjcwODQ0Mg== | ghisvail 1964655 | 2018-02-02T21:10:27Z | 2018-02-02T21:10:27Z | CONTRIBUTOR | Indeed. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
362707544 | https://github.com/pydata/xarray/issues/1879#issuecomment-362707544 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2MjcwNzU0NA== | ghisvail 1964655 | 2018-02-02T21:06:49Z | 2018-02-02T21:06:49Z | CONTRIBUTOR | And what about |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
362705948 | https://github.com/pydata/xarray/issues/1879#issuecomment-362705948 | https://api.github.com/repos/pydata/xarray/issues/1879 | MDEyOklzc3VlQ29tbWVudDM2MjcwNTk0OA== | ghisvail 1964655 | 2018-02-02T21:00:25Z | 2018-02-02T21:00:25Z | CONTRIBUTOR | So, just to confirm, the recommended dependencies are just What about |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Explicit listing of optional dependencies 293830986 | |
292738236 | https://github.com/pydata/xarray/pull/1358#issuecomment-292738236 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjczODIzNg== | ghisvail 1964655 | 2017-04-08T18:54:54Z | 2017-04-08T18:54:54Z | CONTRIBUTOR | And it looks like most projects in the Debian archive using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
292738027 | https://github.com/pydata/xarray/pull/1358#issuecomment-292738027 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjczODAyNw== | ghisvail 1964655 | 2017-04-08T18:51:59Z | 2017-04-08T18:51:59Z | CONTRIBUTOR |
By adding conftest.py manually if that was not clear. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
292737976 | https://github.com/pydata/xarray/pull/1358#issuecomment-292737976 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjczNzk3Ng== | ghisvail 1964655 | 2017-04-08T18:51:13Z | 2017-04-08T18:51:13Z | CONTRIBUTOR | I can get the tests to work at build time, but the CI tests using --pyargs (to test against the installed library under site-packages) no longer do, i.e. I get a bunch of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
292737868 | https://github.com/pydata/xarray/pull/1358#issuecomment-292737868 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjczNzg2OA== | ghisvail 1964655 | 2017-04-08T18:49:23Z | 2017-04-08T18:49:23Z | CONTRIBUTOR | There is a special note for pytest_addoption which might explain the problem. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
292698431 | https://github.com/pydata/xarray/pull/1358#issuecomment-292698431 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjY5ODQzMQ== | ghisvail 1964655 | 2017-04-08T06:23:31Z | 2017-04-08T06:23:31Z | CONTRIBUTOR |
If by packaging you mean distributing here, then I am very disappointed by your statement. From a package maintainer's perspective, I would consider the lack of a test suite a severe regression, should the latter be removed from source distribution in the future. I would also remind you that it is that very same test suite that lead to the triage of the regressions with Please consider fixing the current test suite or reverting to the old design. The fact that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
292494259 | https://github.com/pydata/xarray/pull/1358#issuecomment-292494259 | https://api.github.com/repos/pydata/xarray/issues/1358 | MDEyOklzc3VlQ29tbWVudDI5MjQ5NDI1OQ== | ghisvail 1964655 | 2017-04-07T09:56:39Z | 2017-04-07T09:56:39Z | CONTRIBUTOR | Unfortunately, even if I patch the code base to add the missing file, the tests cannot be run due to the following bug: https://github.com/pytest-dev/pytest/issues/1889 Too bad you guys decided to change the design of the test suite for a point release :-( |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Include missing conftest.py 220160378 | |
285733086 | https://github.com/pydata/xarray/pull/1305#issuecomment-285733086 | https://api.github.com/repos/pydata/xarray/issues/1305 | MDEyOklzc3VlQ29tbWVudDI4NTczMzA4Ng== | ghisvail 1964655 | 2017-03-10T17:34:17Z | 2017-03-10T17:34:17Z | CONTRIBUTOR | I really fail to understand how much of a bug deal it is to introduce a NOTICE file with the right content and keep the LICENSE file and the rest of the code base unchanged. It cannot get any simpler than this. Anyway, your commit provided the missing copyright information I was seeking. For the rest, I gave you a piece of advice for easy compliance (the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Clarify licenses for bundled code 213265588 | |
282557948 | https://github.com/pydata/xarray/issues/1254#issuecomment-282557948 | https://api.github.com/repos/pydata/xarray/issues/1254 | MDEyOklzc3VlQ29tbWVudDI4MjU1Nzk0OA== | ghisvail 1964655 | 2017-02-26T14:02:48Z | 2017-02-26T14:02:48Z | CONTRIBUTOR | FYI, |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide more detailed copyright information 206137485 | |
281805302 | https://github.com/pydata/xarray/issues/1283#issuecomment-281805302 | https://api.github.com/repos/pydata/xarray/issues/1283 | MDEyOklzc3VlQ29tbWVudDI4MTgwNTMwMg== | ghisvail 1964655 | 2017-02-22T21:11:25Z | 2017-02-22T21:11:25Z | CONTRIBUTOR | You meant |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Spurious .DS_Store files in PyPI tarball 209581495 | |
278698787 | https://github.com/pydata/xarray/issues/1254#issuecomment-278698787 | https://api.github.com/repos/pydata/xarray/issues/1254 | MDEyOklzc3VlQ29tbWVudDI3ODY5ODc4Nw== | ghisvail 1964655 | 2017-02-09T16:43:22Z | 2017-02-09T16:43:22Z | CONTRIBUTOR | The complex bit of code embedding is that both MIT and BSD have a clause saying that redistribution from source (even partially) should keep the original copyright notice (which includes authors, dates and license summary). It is straightforward to do when the original file is untouched, however things get a bit more difficult when portions of code gets included in larger modules, or so-called "compatibility" modules, where there is an aggregate of code with mixed copyright. That's why the Did my explanation make sense? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide more detailed copyright information 206137485 | |
278693067 | https://github.com/pydata/xarray/issues/1254#issuecomment-278693067 | https://api.github.com/repos/pydata/xarray/issues/1254 | MDEyOklzc3VlQ29tbWVudDI3ODY5MzA2Nw== | ghisvail 1964655 | 2017-02-09T16:25:24Z | 2017-02-09T16:25:24Z | CONTRIBUTOR | Most Apache-licensed software follow these guidelines, nonetheless. And for the case of Regardless of your decision, I need a comprehensive list of all embedded code which falls under a different copyright than Thanks, |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide more detailed copyright information 206137485 | |
278590912 | https://github.com/pydata/xarray/issues/1254#issuecomment-278590912 | https://api.github.com/repos/pydata/xarray/issues/1254 | MDEyOklzc3VlQ29tbWVudDI3ODU5MDkxMg== | ghisvail 1964655 | 2017-02-09T09:32:36Z | 2017-02-09T09:32:36Z | CONTRIBUTOR |
That is indeed the purpose of the NOTICE file. Since the Apache license state that all source code should start with the Apache copyright header, then individual copyrights from embedded portions of code should be listed in an additional
You do know you are supposed to provide one as per the Apache Software Policy, right? Details about its content and formatting are provided here. I am also providing an example from the ITK project, since you seem to be having doubts about my statement. I can give you many more if your are still not convinced.
Because most projects from the scientific Python stack (including Numpy and Pandas that you mentioned) use the simpler BSD-3-Clause.
Nope, just yourself in this case. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Provide more detailed copyright information 206137485 | |
275392455 | https://github.com/pydata/xarray/issues/1208#issuecomment-275392455 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTM5MjQ1NQ== | ghisvail 1964655 | 2017-01-26T13:51:15Z | 2017-01-26T13:51:15Z | CONTRIBUTOR | Re-opening. Debian now has a version of Numpy with the fix which broke self = <xarray.tests.test_dataarray.TestDataArray testMethod=test_groupby_apply_center>
xarray/tests/test_dataarray.py:1495: xarray/tests/init.py:169: in assertDataArrayAllClose assert_allclose(ar1, ar2, rtol=rtol, atol=atol) xarray/testing.py:125: in assert_allclose assert_allclose(a.variable, b.variable) a = <xarray.Variable (x: 10, y: 20)> array([[ 1.086411e-01, -4.940766e-01, -3.4...e-01, 3.025169e-01, -4.970776e-03, -2.526321e-02, 4.464467e-01]]) b = <xarray.Variable (x: 10, y: 20)> array([[ 1.086411e-01, -4.940766e-01, -3.4...e-01, 3.025169e-01, -4.970776e-03, -2.526321e-02, 4.464467e-01]]) rtol = 1e-05, atol = 1e-08, decode_bytes = True
xarray/testing.py:123: AssertionError _____ TestDataArray.test_groupby_math ______ self = <xarray.tests.test_dataarray.TestDataArray testMethod=test_groupby_math>
xarray/tests/test_dataarray.py:1541: xarray/tests/init.py:169: in assertDataArrayAllClose assert_allclose(ar1, ar2, rtol=rtol, atol=atol) xarray/testing.py:125: in assert_allclose assert_allclose(a.variable, b.variable) a = <xarray.Variable (abc: 3)> array([ 0.504303, -0.53899 , -1.97593 ]) b = <xarray.Variable (abc: 3)> array([ 0.504303, -0.53899 , -0.175924]) rtol = 1e-05, atol = 1e-08, decode_bytes = True
xarray/testing.py:123: AssertionError
----------------------------- Captured stderr call -----------------------------
/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/xarray/tests/test_dataarray.py:1529: FutureWarning: the order of the arguments on DataArray.to_dataset has changed; you now need to supply self = <xarray.tests.test_dataarray.TestDataArray testMethod=test_groupby_sum>
xarray/tests/test_dataarray.py:1440: xarray/tests/init.py:169: in assertDataArrayAllClose assert_allclose(ar1, ar2, rtol=rtol, atol=atol) xarray/testing.py:125: in assert_allclose assert_allclose(a.variable, b.variable) a = <xarray.Variable (abc: 3)> array([ 45.861725, 46.894773, 4.057272]) b = <xarray.Variable (abc: 3)> array([ 45.861725, 46.894773, 0.877923]) rtol = 1e-05, atol = 1e-08, decode_bytes = True
xarray/testing.py:123: AssertionError ============= 3 failed, 1161 passed, 341 skipped in 40.75 seconds ============== ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
273561115 | https://github.com/pydata/xarray/issues/1208#issuecomment-273561115 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3MzU2MTExNQ== | ghisvail 1964655 | 2017-01-18T18:36:38Z | 2017-01-18T18:36:38Z | CONTRIBUTOR | We'd need to wait for numpy-1.12.1 to be absolutely sure. I don't have time to deploy a dev version of numpy to test. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
273559627 | https://github.com/pydata/xarray/issues/1208#issuecomment-273559627 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3MzU1OTYyNw== | ghisvail 1964655 | 2017-01-18T18:31:01Z | 2017-01-18T18:31:01Z | CONTRIBUTOR | It turned out to be a bug in numpy 1.12.0, fixed in 1.12.1, which made |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
272832666 | https://github.com/pydata/xarray/issues/1208#issuecomment-272832666 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3MjgzMjY2Ng== | ghisvail 1964655 | 2017-01-16T11:04:48Z | 2017-01-16T11:04:48Z | CONTRIBUTOR | Thanks, I'll iterate with the Debian maintainer of bottleneck. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
272832299 | https://github.com/pydata/xarray/issues/1209#issuecomment-272832299 | https://api.github.com/repos/pydata/xarray/issues/1209 | MDEyOklzc3VlQ29tbWVudDI3MjgzMjI5OQ== | ghisvail 1964655 | 2017-01-16T11:02:53Z | 2017-01-16T11:02:53Z | CONTRIBUTOR | The build process does run Sphinx so only the source suffices. You don't need to ship a build of the documentation. Indeed wheels should be the preferred mean of installation. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Consider adding the docs to the distributed tarball 200909658 | |
272750949 | https://github.com/pydata/xarray/issues/1167#issuecomment-272750949 | https://api.github.com/repos/pydata/xarray/issues/1167 | MDEyOklzc3VlQ29tbWVudDI3Mjc1MDk0OQ== | ghisvail 1964655 | 2017-01-16T00:39:53Z | 2017-01-16T00:39:53Z | CONTRIBUTOR |
Thanks @shoyer, I used the rc to try out the packaging and give you some initial feedback. See #1208 and #1209. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Things to complete before releasing xarray v0.9.0 195971828 | |
272667110 | https://github.com/pydata/xarray/issues/1167#issuecomment-272667110 | https://api.github.com/repos/pydata/xarray/issues/1167 | MDEyOklzc3VlQ29tbWVudDI3MjY2NzExMA== | ghisvail 1964655 | 2017-01-15T01:39:50Z | 2017-01-15T01:39:50Z | CONTRIBUTOR | @shoyer Do you plan to push a release tarball for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Things to complete before releasing xarray v0.9.0 195971828 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
issue 8