Closed xylar closed 5 years ago
@ocefpaf, since you have a good birds-eye view of conda and conda-forge, I'm wondering if you have thoughts on how you'd like to see this odd case resolved.
I prefer that we drop the the r
in the version. It is better to be PEP 440
compliant. I'm looking into it...
An attempt to install
esmf
with the latestconda
and a spec with a wildcard such as:or
leads to an error like:
The issue seems to be the non-standard
r
at the end of the version number. Conda uses PEP 440 to parse the syntax of version numbers, and the trailingr
doesn't fit into that parsing.This issue could potentially be fixed in
conda
and I'm willing to look into it. But I wondered if it would be feasible to just drop the non-standardr
or in some other way make theesmf
package compatible with the version numbering expected byconda
.See https://github.com/conda/conda/issues/8158 and https://github.com/conda/conda/issues/8309