cftime v1.0.2

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.
Notes and instructions for merging this PR:

1. Please check that the dependencies have not changed.
2. Please merge the PR only after the tests have passed.
3. Feel free to push to the bot's branch to update this PR if needed.
4. The bot will almost always only open one PR per version.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one.

_{This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jhamman]

@jswhit - looks like we have a failing build for windows following the precisions fixes you recently merged.

[jswhit]

Unidata/cftime#76 (branch longdouble) should fix this. If so, I will create a new release.

[jswhit]

cftime 1.0.2.1 release created with this fix

[ocefpaf]

Let's go with #11

PS: I need to check why the failure here was not triggered in the CIs upstream :-/