Proposing `xarray` upstream `entry-points`

Open
#271 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reviewing xarray's existing xarray.backends entry-point convention and the issue's concerns about when entry points should be imported. Work out a proposed naming convention and a concrete example of how pint-xarray would hook into it. Done means a specific, actionable proposal suitable for discussion with xarray upstream.

Written by the indexing model from the issue text.

Description

Having to use import pint_xarray is a bit clunky especially since it does not have explicit usage and can be deleted by some linters. How about proposing xarray upstream to expose a new entry-points to which pint-xarray can hook. They already have xarray.backends, but this feels like it doesn't fit there.

I am opening an issue here because I am not sure about the naming convention to propose, or how to give an example of how the hook should look like, e.g. at which stage should these entry-points be imported at.

Dominant language
Python
Stars
119
Forks
15
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xarray-contrib/pint-xarray

All issues in xarray-contrib/pint-xarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.