-
Notifications
You must be signed in to change notification settings - Fork 298
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
_get_reader_kwargs
is setting kwargs incorrectly.
#2901
Comments
I'm a little confused by your calling structure. |
Ok maybe I shouldn't say "never", it looks like you are passing them in the right order. What exactly are you passing in your example code? |
I think more important is this function which gets called first (before satpy/satpy/readers/__init__.py Lines 606 to 618 in ee2273a
If I understood your use on slack, you're passing filenames from find_files_and_readers so your filenames are probably |
Quick comment as it's late here:
|
I'm unable to reproduce this with what I assume would be equivalent:
Same result if I remove the |
Describe the bug
The function
_get_reader_kwargs
insatpy/satpy/readers/__init__.py
is incorrectly setting thereader_kwargs
in some circumstances. Rather than setting toreader_kwargs = {"reader_name": {}}
, it instead returns a dict composed of thereader
name.To Reproduce
Stepping through the code with the debugger, I see this:
In the
__init__.py
file.In the above example,
reader
is notNone
, but we're not passing anyreader_kwargs
to this function, so in theelif
we end up settingreader_kwargs
to `{'r': [], 'e': [], 'a': [], 'd': []} or whatever the reader is called.As satpy seems to work OK this is probably not a big deal, but I presume it should be fixed!
The text was updated successfully, but these errors were encountered: