home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 164093345

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/645#issuecomment-164093345 https://api.github.com/repos/pydata/xarray/issues/645 164093345 MDEyOklzc3VlQ29tbWVudDE2NDA5MzM0NQ== 5635139 2015-12-12T01:21:12Z 2015-12-12T06:03:10Z MEMBER

@shoyer Coming back to this:

The main subtlety is that currently we don't actually create the pandas.Index object until we load the entire index array into memory or need to do a lookup operation on the index. I'm not entirely sure this laziness is necessary, but it might be helpful -- it lets us differ loading some data from disk (or remote data sources) until absolutely necessary.

How expensive / inconvenient would it be to force only the coordinate dims to be eagerly loaded? There are some real benefits of having the coordinate dims be pandas Indexes, such as string coercion on dates, full PeriodIndex support, and tz support (and would it make some slicing & MultiIndexes easier too?). If the adaptors are there only to enable lazy loading, is that a worthwhile tradeoff?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  115210260
Powered by Datasette · Queries took 0.904ms · About: xarray-datasette