home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "NONE" and issue = 832404698 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

  • FFY00 2
  • eli-schwartz 1

issue 1

  • [tests] ImportError: Pandas requires version '0.12.3' or newer of 'xarray' (version '0.0.0' currently installed). · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
800572482 https://github.com/pydata/xarray/issues/5038#issuecomment-800572482 https://api.github.com/repos/pydata/xarray/issues/5038 MDEyOklzc3VlQ29tbWVudDgwMDU3MjQ4Mg== eli-schwartz 6551424 2021-03-16T20:15:38Z 2021-03-16T20:15:38Z NONE

My guess is that this started to fail because we moved the setup_requires entry to pyproject.toml, which means that if you don't use that you have to take care of the build dependencies yourself.

Current versions of setuptools use pip instead of easy_install, so moving the setup_requires back would result in setup.py reporting an error when it cannot find setuptools_scm and pip is not installed in the build chroot.

The pyproject.toml build-system.requires is not exclusive; PEP 517 <build-backend>.get_requires_for_build_wheel() will be added to it to create the complete list of build requirements; the pyproject.toml build-system.requires is only needed to bootstrap the build backend itself.

And since the build backend when run on its own does not support pyproject.toml, but setuptools_scm is an internal implementation detail of the build backend and NOT of the PEP 517 part of the story... I'd personally say that it belongs in setup.cfg setup_requires rather than pyproject.toml

YMMV

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  [tests] ImportError: Pandas requires version '0.12.3' or newer of 'xarray' (version '0.0.0' currently installed).  832404698
800289142 https://github.com/pydata/xarray/issues/5038#issuecomment-800289142 https://api.github.com/repos/pydata/xarray/issues/5038 MDEyOklzc3VlQ29tbWVudDgwMDI4OTE0Mg== FFY00 11718923 2021-03-16T14:09:57Z 2021-03-16T14:41:32Z NONE

We should not be using build in arch packaging yet as other team members do not like pip as a wheel installer. We are working on that in https://github.com/pradyunsg/installer.

Can you see if setting SETUPTOOLS_SCM_PRETEND_VERSION solves your issue? https://github.com/archlinux/svntogit-community/blob/d5d26f0836c57a20cbd6162a301c78ea60fc0845/trunk/PKGBUILD#L20

If setuptools-scm can't find a version I don't understand why it isn't falling back to 999. @keewis, did anyone actually test this change? https://github.com/pydata/xarray/blob/master/setup.py#L4

If what I said doesn't work, please try adding python-toml to makedepends so that setuptools picks up pyproject.toml.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  [tests] ImportError: Pandas requires version '0.12.3' or newer of 'xarray' (version '0.0.0' currently installed).  832404698
800312893 https://github.com/pydata/xarray/issues/5038#issuecomment-800312893 https://api.github.com/repos/pydata/xarray/issues/5038 MDEyOklzc3VlQ29tbWVudDgwMDMxMjg5Mw== FFY00 11718923 2021-03-16T14:35:37Z 2021-03-16T14:35:37Z NONE

That is fine. @ArchangeGabriel this should be solved by adding python-setuptools-scm to makedepends and then either building from git or a PyPI tarball (sdist) or setting SETUPTOOLS_SCM_PRETEND_VERSION.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  [tests] ImportError: Pandas requires version '0.12.3' or newer of 'xarray' (version '0.0.0' currently installed).  832404698

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 16.752ms · About: xarray-datasette