Skip to content

MNT: Run PTH flake test in prep for supporting pathlib (wcs)#16936

Closed
neutrinoceros wants to merge 2 commits intoastropy:mainfrom
neutrinoceros:wcs/rfc/pth_checks
Closed

MNT: Run PTH flake test in prep for supporting pathlib (wcs)#16936
neutrinoceros wants to merge 2 commits intoastropy:mainfrom
neutrinoceros:wcs/rfc/pth_checks

Conversation

@neutrinoceros
Copy link
Contributor

Description

Extracted from #16060. Ref #16924

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2024

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.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2024

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

@neutrinoceros neutrinoceros marked this pull request as ready for review September 4, 2024 10:11
@pllim pllim added this to the v7.0.0 milestone Sep 4, 2024
@pllim pllim added the Extra CI Run cron CI as part of PR label Sep 4, 2024
@neutrinoceros neutrinoceros force-pushed the wcs/rfc/pth_checks branch 2 times, most recently from 5ff91c3 to 667e602 Compare September 5, 2024 11:22
@neutrinoceros neutrinoceros marked this pull request as draft September 5, 2024 11:28
@astrofrog astrofrog removed their request for review September 5, 2024 14:09
@neutrinoceros neutrinoceros marked this pull request as ready for review September 10, 2024 18:21
@neutrinoceros
Copy link
Contributor Author

If I understand correctly this is waiting on a new extension-helpers release (@astrofrog), but it also look like the PR could go in without it.
@nstarman what do you think ?

@neutrinoceros neutrinoceros force-pushed the wcs/rfc/pth_checks branch 2 times, most recently from 470e71b to 8579ab1 Compare October 16, 2024 08:21
@astrofrog
Copy link
Member

@neutrinoceros - FYI I've just triggered a 1.2.0 release of extension-helpers: https://github.com/astropy/extension-helpers/releases/tag/v1.2.0 - build ongoing

@neutrinoceros neutrinoceros marked this pull request as draft October 16, 2024 14:27
@neutrinoceros
Copy link
Contributor Author

Thanks @astrofrog ! I took advantage of it to simplify this PR

@neutrinoceros neutrinoceros marked this pull request as ready for review October 16, 2024 14:34
@neutrinoceros
Copy link
Contributor Author

neutrinoceros commented Oct 16, 2024

whoops, I neglected that we cannot trivially bump build time dependencies without breaking exotic archs, so let me postpone this last commit to a follow up PR.

update: this is #17193

@neutrinoceros
Copy link
Contributor Author

We're hours away from astropy 7.0's feature freeze and this shouldn't be blocking in any way, so I'll bump the milestone to clear the backlog. If this happened to be merged today anyway, please revert the milestone.

@neutrinoceros neutrinoceros modified the milestones: v7.0.0, v7.1.0 Oct 25, 2024
@github-actions github-actions bot added the Close? Tell stale bot that this issue/PR is stale label Mar 16, 2025
@github-actions
Copy link
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 4 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.

def test_tpv_ctype_tan():
sip_header = fits.Header.fromstring(
get_pkg_data_contents(os.path.join("data", "siponly.hdr"), encoding="binary")
get_pkg_data_contents(Path("data") / "siponly.hdr", encoding="binary")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe consolidate the Path("data") here and below into a variable?
Actually, make it a pytest fixture! It's used all over this file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually! put it in wcs/tests/conftest.py then it can be used across all the wcs/tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, I'm not convinced that such a small fixture is worth adding an indirection to all tests that would use it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure.

Co-authored-by: Mridul Seth <git@mriduls.com>
@neutrinoceros
Copy link
Contributor Author

@nstarman thank you for picking this up. I should have addressed all your points.

@nstarman
Copy link
Member

@neutrinoceros more test coverage needed?

@neutrinoceros
Copy link
Contributor Author

done

Copy link
Member

@nstarman nstarman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the followup to un-stringify some of these paths, LGTM! Thanks @neutrinoceros.
Whom else needs to approve?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm low level API is bound by https://github.com/astropy/astropy-APEs/blob/main/APE14.rst . Does GWCS need to buy in also? cc @astrofrog @Cadair @nden

@astrofrog astrofrog modified the milestones: v7.1.0, v7.2.0 Apr 28, 2025
@pllim
Copy link
Member

pllim commented Jun 18, 2025

Given the recent revert of PTH changes, let's not do this for now. Thanks anyway!

@pllim pllim closed this Jun 18, 2025
@neutrinoceros neutrinoceros deleted the wcs/rfc/pth_checks branch June 18, 2025 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Close? Tell stale bot that this issue/PR is stale dev-automation Extra CI Run cron CI as part of PR testing wcs.wcsapi wcs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants