import and call the env analysis script #4
Conversation
|
Will need more python tests, but this does include all the failure conditions in the end-to-end tests. We'll need to figure out how to automatically bump the failing envs, though. |
envs/env1.yaml
Outdated
|
|
||
|
|
||
| def is_preview(version): | ||
| candidates = ["rc", "beta", "alpha"] |
There was a problem hiding this comment.
| candidates = ["rc", "beta", "alpha"] | |
| candidates = ("rc", "b", "a") |
I think PEP440 wants "a" and "b" for alpha and beta releases (not sure what rattler does of course)
There was a problem hiding this comment.
rattler doesn't do anything different, the versions are those on conda-forge. I don't know if that always has the same rules as PyPI.
I haven't seen alpha/beta releases on conda-forge, yet, though, so those are there for completeness. I'd also go with a set literal instead of tuple/list literals.
Co-authored-by: Mathias Hauser <[email protected]>
|
|
||
|
|
||
| def is_preview(version): | ||
| candidates = ["rc", "beta", "alpha"] |
There was a problem hiding this comment.
rattler doesn't do anything different, the versions are those on conda-forge. I don't know if that always has the same rules as PyPI.
I haven't seen alpha/beta releases on conda-forge, yet, though, so those are there for completeness. I'd also go with a set literal instead of tuple/list literals.
(from pydata/xarray#9754)