Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

DEP: forbid source installs of hypothesis through uv#20126

Merged
pllim merged 1 commit into
astropy:mainastropy/astropy:mainfrom
neutrinoceros:dep/no-build-hypothesisneutrinoceros/astropy:dep/no-build-hypothesisCopy head branch name to clipboard
Jul 24, 2026
Merged

DEP: forbid source installs of hypothesis through uv#20126
pllim merged 1 commit into
astropy:mainastropy/astropy:mainfrom
neutrinoceros:dep/no-build-hypothesisneutrinoceros/astropy:dep/no-build-hypothesisCopy head branch name to clipboard

Conversation

@neutrinoceros

@neutrinoceros neutrinoceros commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Description

Now that hypothesis isn't a pure-Python package anymore, it makes sense to require binary installs everywhere.

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

@neutrinoceros neutrinoceros added this to the v8.1.0 milestone Jul 24, 2026
@neutrinoceros neutrinoceros added testing no-changelog-entry-needed dependencies Pull requests that update a dependency file labels Jul 24, 2026
@github-actions

github-actions Bot commented Jul 24, 2026

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?
  • 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 approved these changes Jul 24, 2026
View reviewed changes

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

@pllim
pllim merged commit 4ea9e25 into astropy:main Jul 24, 2026
46 of 49 checks passed
@neutrinoceros
neutrinoceros deleted the dep/no-build-hypothesis branch July 24, 2026 21:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pllim pllim pllim approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file no-changelog-entry-needed testing

Projects

None yet

Milestone

v8.1.0

Development

Successfully merging this pull request may close these issues.

2 participants

@neutrinoceros @pllim
Morty Proxy This is a proxified and sanitized view of the page, visit original site.