We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While testing the docstrings I thing I found a bug here:
https://github.com/SciTools/cf_units/blob/master/units/unit.py#L637
date2num is in netcdftime.utime.date2num now, see Unidata/netcdf4-python@4d48266
date2num
netcdftime.utime.date2num
@rhattersley should I fix this or pin a netcdftime version?
The text was updated successfully, but these errors were encountered:
I think we need to manage the two for a period. I'm afraid it is going to have to look something like:
try: import netcdftime.utime.date2num as date2num except ImportError: import netcdftime.date2num as date2num
Unless a more elegant solution can be found.
Sorry, something went wrong.
cf_units
The utime class exists in all version. So I think we are good if we change the calls to netcdftime.date2num for
utime
netcdftime.date2num
t = netcdftime.utime('hours since 0001-01-01 00:00:00', calendar='standard') t.date2num(datetime.strptime('3/14/15 9:26:53', '%m/%d/%y %H:%M:%S'))
I will test that as soon as #13 gets merged.
is_vertical
c6bf2e4
Merge pull request #16 from ocefpaf/netcdftime
a9007b8
Fix #14.
No branches or pull requests
While testing the docstrings I thing I found a bug here:
https://github.com/SciTools/cf_units/blob/master/units/unit.py#L637
date2num
is innetcdftime.utime.date2num
now, see Unidata/netcdf4-python@4d48266@rhattersley should I fix this or pin a netcdftime version?
The text was updated successfully, but these errors were encountered: