-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dim
vs dims
#6646
Labels
Comments
I've noticed this before and do find it a bit annoying. |
It would be helpful to understand if there are also other uses of |
NumPy mostly uses |
As discussed on the dev call — we can plan to move to |
max-sixty
added a commit
to max-sixty/xarray
that referenced
this issue
Nov 28, 2023
Begins the process of pydata#6646. I don't think it's feasible / enjoyable to do this for everything at once, so I would suggest we do it gradually, while keeping the warnings quite quiet, so by the time we convert to louder warnings, users can do a find/replace easily.
max-sixty
added a commit
that referenced
this issue
Nov 28, 2023
* Start renaming `dims` to `dim` Begins the process of #6646. I don't think it's feasible / enjoyable to do this for everything at once, so I would suggest we do it gradually, while keeping the warnings quite quiet, so by the time we convert to louder warnings, users can do a find/replace easily. * No deprecation for internal methods * Simplify typing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your issue?
I've recently been hit with this when experimenting with
xr.dot
andxr.corr
—xr.dot
takesdims
, andxr.cov
takesdim
. Because they each take multiple arrays as positional args, kwargs are more conventional.Should we standardize on one of these?
The text was updated successfully, but these errors were encountered: