Skip to content

Run pip check during tests - #19

Closed
MridulS wants to merge 1 commit into
conda-forge:mainfrom
MridulS:MridulS-patch-1
Closed

Run pip check during tests#19
MridulS wants to merge 1 commit into
conda-forge:mainfrom
MridulS:MridulS-patch-1

Conversation

@MridulS

@MridulS MridulS commented Aug 19, 2026

Copy link
Copy Markdown
Member

This ensures that there isn't a drift between pypi and conda metadata.
While adding sans-fitter to conda-forge I ran into a pip check failure as the sasmodels pypi package depends on tccbox and columnize but those packages aren't present in the conda recipe. The pip check will catch these failures earlier. Keeping it draft first to test out the CI.

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

This ensures that there isn't a drift between pypi and conda metadata
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@MridulS

MridulS commented Aug 19, 2026

Copy link
Copy Markdown
Member Author

It fails as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants