home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

8 rows where issue = 430214243 and user = 6213168 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • crusaderky · 8 ✖

issue 1

  • WIP: type annotations · 8 ✖

author_association 1

  • MEMBER 8
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
481779522 https://github.com/pydata/xarray/pull/2877#issuecomment-481779522 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MTc3OTUyMg== crusaderky 6213168 2019-04-10T17:11:27Z 2019-04-10T17:11:27Z MEMBER

@shoyer implemented all change requests except OrderedDict

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
481739493 https://github.com/pydata/xarray/pull/2877#issuecomment-481739493 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MTczOTQ5Mw== crusaderky 6213168 2019-04-10T15:29:04Z 2019-04-10T15:29:04Z MEMBER

@shoyer I changed dimensions from str to Hashable as requested. In my opinion however it's not great, because 1. it's currently thoroughly broken due to lack of unit tests 2. it weakens type checking a lot, since Tuple is a subclass of Hashable however the vast majority of xarray functions deal with tuples with a specific code branch

Please review again - in theory, common.py and util.py are now 100% done. They pass flake8 and mypy (on python 3.7). If you like them please go on and merge into Master; since the work that needs to be done is going to touch literally everything I think it's best to break it down into more manageable chunks.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480782801 https://github.com/pydata/xarray/pull/2877#issuecomment-480782801 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc4MjgwMQ== crusaderky 6213168 2019-04-08T10:51:35Z 2019-04-08T10:51:35Z MEMBER

Opened https://bugs.python.org/issue36555

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480767658 https://github.com/pydata/xarray/pull/2877#issuecomment-480767658 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc2NzY1OA== crusaderky 6213168 2019-04-08T10:01:26Z 2019-04-08T10:01:26Z MEMBER

@shoyer I have a problem. In Python 3.5.0-3.5.2, to create a custom typed collection you have to write class Frozen(collections.abc.Mapping, typing.Mapping[K, V]): Whereas in Python >= 3.5.3, you must just write class Frozen(typing.Mapping[K, V]): Things won't work if you use the < 3.5.3 syntax.

As an unrelated note, I'm observing that if I set python=3.5.3 in ci/requirements-py35.yml, a ton of unit tests fall apart. The test suite ci/requirements-py35-min.yml ensures compatibility with Python 3.5.0... but only as long as you don't use any of the non-mandatory dependencies. Can we 1) increase the minimum requirements to 3.5.4 and 2) set python=3.5.4 in ci/requirements-py35.yml? Is there a roadmap for dropping 3.5 entirely? (conda-forge already did...)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480756652 https://github.com/pydata/xarray/pull/2877#issuecomment-480756652 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc1NjY1Mg== crusaderky 6213168 2019-04-08T09:29:29Z 2019-04-08T09:29:29Z MEMBER

Mmh it looks like if I run mypy in Python 3.7 I get a much terser output. Still some horrible broken things to care about, like the fact that in 3.5 typing.Mapping did not inherit from collections.abc.Mapping, but they can be worked around somehow.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480752288 https://github.com/pydata/xarray/pull/2877#issuecomment-480752288 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc1MjI4OA== crusaderky 6213168 2019-04-08T09:16:51Z 2019-04-08T09:16:51Z MEMBER

@shoyer I am using mypy. But unlike flake8 I don't think I'll be able to integrate it in CI. This error doesn't make any sense to me: xarray/core/common.py:124: error: Overloaded function signatures 1 and 2 overlap with incompatible return types

These I think are unfixable in Python 3.5, as I can't declare these under the class definition: xarray/core/utils.py:445: error: "NdimSizeLenMixin" has no attribute "shape" xarray/core/utils.py:450: error: "NdimSizeLenMixin" has no attribute "shape" xarray/core/utils.py:454: error: "NdimSizeLenMixin" has no attribute "shape" xarray/core/utils.py:468: error: "NDArrayMixin" has no attribute "array" xarray/core/utils.py:472: error: "NDArrayMixin" has no attribute "array" xarray/core/utils.py:478: error: "NDArrayMixin" has no attribute "array" xarray/core/common.py:151: error: "AbstractArray" has no attribute "dims" xarray/core/common.py:154: error: "AbstractArray" has no attribute "dims" xarray/core/common.py:166: error: "AbstractArray" has no attribute "dims" xarray/core/common.py:166: error: "AbstractArray" has no attribute "shape" xarray/core/common.py:896: error: Cannot determine type of '_file_obj' xarray/core/common.py:897: error: Cannot determine type of '_file_obj' (additionally, typing doesn't offer anything for "file-like" objects)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480741636 https://github.com/pydata/xarray/pull/2877#issuecomment-480741636 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc0MTYzNg== crusaderky 6213168 2019-04-08T08:45:42Z 2019-04-08T08:45:42Z MEMBER

From the 3.5.2 release notes:

A new version of typing.py provides several new classes and features: @overload outside stubs, Reversible, DefaultDict, Text, ContextManager, Type[], NewType(), TYPE_CHECKING, and numerous bug fixes (note that some of the new features are not yet implemented in mypy or other static analyzers). Also classes for PEP 492 (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact they made it into 3.5.1 but were never mentioned).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243
480740633 https://github.com/pydata/xarray/pull/2877#issuecomment-480740633 https://api.github.com/repos/pydata/xarray/issues/2877 MDEyOklzc3VlQ29tbWVudDQ4MDc0MDYzMw== crusaderky 6213168 2019-04-08T08:42:48Z 2019-04-08T08:42:48Z MEMBER

@shoyer how do you feel about raising the minimum Python version to 3.5.2? There's quite a bit of important stuff in it, some of which undocumented. Namely @overload doesn't work with 3.5.0 (although I could conditionally replace it with a no-op thorough a backport module).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  WIP: type annotations 430214243

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

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]);
Powered by Datasette · Queries took 36.876ms · About: xarray-datasette