Skip to content

Deprecate unused introspection functions - #15934

Merged
pllim merged 2 commits into
astropy:mainfrom
eerovaher:introspection-deprecations
Jan 23, 2024
Merged

pllim merged 2 commits into
astropy:mainfrom
eerovaher:introspection-deprecations

Conversation

@eerovaher

Copy link
Copy Markdown
Member

Description

astropy.utils.introspection.isinstancemethod() isn't used anywhere (since 9bbdd64) and should be safe to remove without replacement. Previously the function simply called a private function that contained the actual implementation. I have removed the private function to ensure that it doesn't stay in the code when the public function gets removed. I have also removed examples from the function docstring to avoid having to deal with deprecation warnings there.

astropy.utils.introspection.find_mod_objs() was used for automatically generating API listings for Sphinx, but that functionality has since been moved from astropy to a dedicated sphinx-automodapi package that has its own find_mod_objs(): https://github.com/astropy/sphinx-automodapi/blob/7c57ce13320e8b0448e75e4d8300748a914fa2cb/sphinx_automodapi/utils.py#L40. The implementation in astropy is no longer used anywhere and should be safe to remove without replacement.

  • 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.

The function is not used anywhere in `astropy`.
The function is not used anywhere in `astropy`.
@eerovaher eerovaher added utils API change PRs and issues that change an existing API, possibly requiring a deprecation period labels Jan 23, 2024
@eerovaher eerovaher added this to the v6.1.0 milestone Jan 23, 2024
@github-actions

Copy link
Copy Markdown
Contributor

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?
  • Is a milestone set? Milestone must be set but we cannot check for it on Actions; do not let the green checkmark fool you.
  • 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.

@pllim pllim left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Seems reasonable. Thanks for the clean-up!

Let's get this in earlier than later so downstream has a chance to catch this if they somehow using these.

@pllim
pllim merged commit 79be57e into astropy:main Jan 23, 2024
@eerovaher
eerovaher deleted the introspection-deprecations branch January 24, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

API change PRs and issues that change an existing API, possibly requiring a deprecation period utils

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants