Skip to content

Conversation

@dschwoerer
Copy link
Contributor

I think it is best to completely remove the warning.
As a user I do not want to first figure out how many files I will be opening, and then set that with xarray to avoid a warning.

It was broken anyway, as it did always raise the warning, so I think it is best to remove the warning completely.

The first commit a4c0996 is still needed, as otherwise we may lower the limit, which is needed for other things.

@dschwoerer dschwoerer added the bugfix Fix for a bug label Nov 28, 2025
Copy link
Member

@ZedThree ZedThree left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not convinced of the wisdom of changing file_cache_maxsize like this, but I don't know the ins and outs of it. This change seems reasonable though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Fix for a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants