Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added a recipe for pytransit. #28286

Merged
merged 4 commits into from
Nov 26, 2024
Merged

Added a recipe for pytransit. #28286

merged 4 commits into from
Nov 26, 2024

Conversation

hpparvi
Copy link
Contributor

@hpparvi hpparvi commented Nov 20, 2024

This PR adds a recipe for the pytransit package for exoplanet transit modelling.

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
  • License file is packaged (see here for an example).
  • Source is from official source.
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
  • If static libraries are linked in, the license of the static library is packaged.
  • Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
  • Build number is 0.
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
  • GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
  • When in trouble, please check our knowledge base documentation before pinging a team.

Copy link

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

@conda-forge-admin
Copy link
Contributor

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

I wanted to let you know that I linted all conda-recipes in your PR (recipes/pytransit/meta.yaml) and found some lint.

Here's what I've got...

For recipes/pytransit/meta.yaml:

  • ❌ The home item is expected in the about section.

For recipes/pytransit/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
    • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).
  • ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

Copy link
Contributor

@mwcraig mwcraig left a comment

Choose a reason for hiding this comment

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

Thanks for opening this, @hpparvi! Just a few minor suggestions and it should be ready to go.

recipes/pytransit/meta.yaml Outdated Show resolved Hide resolved
recipes/pytransit/meta.yaml Outdated Show resolved Hide resolved
recipes/pytransit/meta.yaml Show resolved Hide resolved
recipes/pytransit/meta.yaml Show resolved Hide resolved
@conda-forge-admin
Copy link
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 (recipes/pytransit/meta.yaml) and found it was in an excellent condition.

@hpparvi
Copy link
Contributor Author

hpparvi commented Nov 26, 2024

Many thanks for your comments @mwcraig! The recipe should now be ready for review.

@hpparvi
Copy link
Contributor Author

hpparvi commented Nov 26, 2024

@conda-forge/help-python, ready for review!

@mwcraig mwcraig merged commit c47759a into conda-forge:main Nov 26, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants