Skip to content
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

kwarg defaults (join="inner") for DataArray._binary_ops() #1059

Closed
chunweiyuan opened this issue Oct 25, 2016 · 5 comments
Closed

kwarg defaults (join="inner") for DataArray._binary_ops() #1059

chunweiyuan opened this issue Oct 25, 2016 · 5 comments
Labels

Comments

@chunweiyuan
Copy link
Contributor

Currently the default is join="inner". However, there can be applications where the majority of binary operations require join="outer", not "inner".

Would it be advisable to place these default values in some config object the user can set at the beginning of the run script? Or perhaps one already exists but I've failed to locate it.

@shoyer
Copy link
Member

shoyer commented Oct 25, 2016

Yes, we could make this a configurable option (currently it is not). See xarray.set_options for some related machinery.

@chunweiyuan
Copy link
Contributor Author

Thanks. I will soon submit a pull request from my fork. Which branch should it go to? It seems that many people submit pull requests to master here.

@shoyer
Copy link
Member

shoyer commented Oct 27, 2016

We submit PRs to master. Please also be sure to update Dataset binary ops,
too.

On Thu, Oct 27, 2016 at 1:55 PM, chunweiyuan notifications@github.com
wrote:

Thanks. I will soon submit a pull request from my fork. Which branch
should it go to? It seems that many people submit pull requests to master
here.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1059 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKS1uoiRC1_HY1NQdIdO8aEhOq9gGHjks5q4Q_CgaJpZM4KfjtM
.

@chunweiyuan
Copy link
Contributor Author

Yup, did that. Thank you. Will request to have you as a reviewer. Much obliged.

@stale
Copy link

stale bot commented Jan 25, 2019

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity
If this issue remains relevant, please comment here; otherwise it will be marked as closed automatically

@stale stale bot added the stale label Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants