-
Notifications
You must be signed in to change notification settings - Fork 11
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
default_version
arg. to NetCDFRead.read
not exposed: remove?
#298
Comments
default_version
argument is not exposed to user: remove it?default_version
argument to NetCDFRead.read
not exposed to user
default_version
argument to NetCDFRead.read
not exposed to userdefault_version
argument to NetCDFRead.read
not exposed: remove?
default_version
argument to NetCDFRead.read
not exposed: remove?default_version
arg. to NetCDFRead.read
not exposed: remove?
There is another parameter I would like to expose in That said, I think it could be a useful user-facing method - so I propose to upgrade it to one, possibly as part of the API review for cf v4.0.0. |
Hi Sadie - what is the use case for querying the |
In #296 I want to check that the correct |
Is the answer to that to add those keys to the DEBUG logging from |
I have done that already and so I guess we can indeed test by searching for the 'file_version' result in the log output string, and that would mean no need to expose the |
The netCDF-specific
read
, i.e.NetCDFRead.read
method, has an argumentdefault_version
which isn't documented but according to a comment over logic using the corresponding variable, it supports a "default version provided by the user" for the Conventions:cfdm/cfdm/read_write/netcdf/netcdfread.py
Lines 774 to 778 in e948eef
however in our user-exposed
read
function, there is no way to access it:cfdm/cfdm/read_write/read.py
Lines 11 to 21 in e948eef
so there is no way to apply that in the intended way, as a user. It is not documented at all across the documentation either.
It seems like this is dead code which needs to be removed, but I've opened this as a question in case we instead want to revive it by exposing it through the
read
function. @davidhassell, what do you think is best?If we want to remove the several lines of logic that concern it, I can do so as part of #296 which touches the same area of code.
The text was updated successfully, but these errors were encountered: