Exclude structured_units.rst for erfa-dev#18551
Conversation
|
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
|
Hmm, this passed the relevant test, but not "load tox environments", for reasons that seem unrelated. |
|
@pllim - thanks, how can I not have seen that? Hopefully things still work, if not I'll check locally. |
|
You might need to tag a new dev tag over at pyerfa or something because devdeps is picking up the following version and still failing: Also we pick up pyerfa-dev from https://pypi.anaconda.org/liberfa/simple so please make sure the dev wheel with new tag is pushed there before rerunning devdeps here. Thanks! |
f427ad0 to
207297c
Compare
|
Gee, where was my brain yesterday? Not only got the name wrong, as you noticed, but also the actual version number - 2.1.0.7 is the actual next release that is in development. Also, for some reason, v2.1.0.6 never got properly released (was relevant for infrastructure mostly, so no big deal, but I should have noticed it...). Anyway, hopefully things will now just work. |
| dependencies = [ | ||
| "numpy>=1.24", | ||
| "pyerfa>=2.0.1.1", | ||
| "pyerfa>=2.0.1.1", # For >=2.0.1.8, adjust structured_units.rst and doctest-requires |
There was a problem hiding this comment.
| "pyerfa>=2.0.1.1", # For >=2.0.1.8, adjust structured_units.rst and doctest-requires | |
| "pyerfa>=2.0.1.1", # For >=2.0.1.7, adjust structured_units.rst and doctest-requires |
|
Yikes, still not working. Will investigate locally. |
207297c to
0e051d9
Compare
|
Dyslexia too, apparently... 2.1.0.7 or 2.0.1.7. Sigh. |
Wow I missed that too! |
|
Looks like it passed now... |
Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com>
|
OK, done. Thanks, @pllim, and apologies for all the silly mistakes in a 2-line changed PR... |
pllim
left a comment
There was a problem hiding this comment.
No worries. Thanks for the fix!
|
Actually maybe we should backport to future-proof the release branch CI @meeseeksdev backport to v7.1.x |
This comment was marked as resolved.
This comment was marked as resolved.
|
Hmm. Let me rerun devdeps on v7.1.x to make sure. (Yes, fails now, so we need the backport.) |
* Exclude structured_units.rst for erfa-dev * Update pyproject.toml [skip ci] Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com> --------- Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com> (cherry picked from commit 674c737)
|
Manual backport at #18554 |
* Exclude structured_units.rst for erfa-dev * Update pyproject.toml Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com> --------- Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com> (cherry picked from commit 674c737)
Backport PR #18551 on branch v7.1.x (Exclude structured_units.rst for erfa-dev)
|
I'm running into the comment from this PR in #19380, and I don't think I understand the note at all... pyerfa 2.0.1.7 doesn't exist yet ? even 2.0.1.6 is in the future, so why was an hypothetical future version even mentioned ? |
|
I think this was to future proof. |
|
It was to future proof indeed, with 2.0.1.7 meant to be the next release up. Looking at |
Description
This pull request is to address the failure from a recent update in erfa. Similar to #18549, but just avoids running the doctest with erfa-dev (which should be fine). Main advantage is that there is a note to undo...