home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 124129804

This data as json

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
124129804 MDU6SXNzdWUxMjQxMjk4MDQ= 687 Dataset.T property creates conflict with data named 'T' 9097307 closed 0     3 2015-12-28T21:30:58Z 2015-12-29T03:09:47Z 2015-12-29T03:09:47Z CONTRIBUTOR      

I frequently find myself working with datasets that include a variable named 'T' (for temperature!)

The problem with this is that, unlike any other variable, mydataset.T does not return the variable, because there is a built-in property .T which is just a map to the mydataset.transpose() method.

This is mostly just a minor annoyance, because of course I can access the data as mydataset['T'], but it necessitates an odd asymmetry in any code that accesses T as well as other data. And, maybe more importantly, mydataset.T does NOT immediately raise an error in code that is attempting to access the temperature data.

I have not been able to simply remove the property interactively from the dataset objects, e.g. del mydataset.T raises an error AttributeError: can't delete attribute

Since the transpose functionality is already easily accessible through mydataset.transpose() (which is more readable, in my opinion), perhaps the T property should just be removed?

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/687/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed 13221727 issue

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 3 rows from issue in issue_comments
Powered by Datasette · Queries took 240.557ms · About: xarray-datasette