Skip to content

Conversation

@mjwillson
Copy link
Contributor

@mjwillson mjwillson commented Nov 22, 2025

This determines how non-index coordinates of the same name are compared for potential conflicts when performing binary operations.

The default is compat='minimal', which matches the previous behvaiour.

I had originally planned to set this up to migrate the default to arithmetic_compat='override' alongside the wider migration of default to compat='override' elsewhere. However I've held off on this for now pending a decision on what to do anything about the original motivation of compat='minimal' here which was to drop clashing scalar coordinates that arise from things like arr[0] + arr[1].

  • Tests added
  • User visible changes (including notable bug fixes) are documented in whats-new.rst

@welcome
Copy link

welcome bot commented Nov 22, 2025

Thank you for opening this pull request! It may take us a few days to respond here, so thank you for being patient.
If you have questions, some answers may be found in our contributing guidelines.

@mjwillson mjwillson force-pushed the non_index_coords_compat_override branch 3 times, most recently from a1af177 to 4c5a3a4 Compare November 24, 2025 12:44
…ow non-index coordinates of the same name are compared for potential conflicts when performing binary operations.

The default of compat='minimal' matches the previous behaviour.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant