Skip to content
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

Wrong dtype of return in date2num #202

Open
zklaus opened this issue Oct 27, 2021 · 0 comments · May be fixed by #467
Open

Wrong dtype of return in date2num #202

zklaus opened this issue Oct 27, 2021 · 0 comments · May be fixed by #467
Assignees
Labels
community Good First Issue A good issue to take on if you're just getting started with cf-units development New: Documentation Highlight a new community raised "documentation" issue Type: Documentation

Comments

@zklaus
Copy link

zklaus commented Oct 27, 2021

📚 Documentation

The documentation for cf_units.Unit.date2num and cf_units.date2num stipulates that both functions return a float, or numpy.ndarray of floats. However, since the return value comes directly from cftime.date2num, this will regularly return "an array of integers" since cftime version 1.4.0 (see the changelog).

@zklaus zklaus added New: Documentation Highlight a new community raised "documentation" issue Type: Documentation labels Oct 27, 2021
@rcomer rcomer added the Good First Issue A good issue to take on if you're just getting started with cf-units development label Oct 31, 2021
@rcomer rcomer mentioned this issue May 26, 2022
@pp-mo pp-mo assigned ukmo-ccbunney and pp-mo and unassigned ukmo-ccbunney and pp-mo Sep 20, 2024
@ukmo-ccbunney ukmo-ccbunney linked a pull request Sep 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Good First Issue A good issue to take on if you're just getting started with cf-units development New: Documentation Highlight a new community raised "documentation" issue Type: Documentation
Projects
Status: In progress
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants