Skip to content

Conversation

@changliao1025
Copy link
Contributor

@changliao1025 changliao1025 commented Jan 20, 2026

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.

Copilot AI review requested due to automatic review settings January 20, 2026 04:55
@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/pyearthviz/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/pyearthviz/recipe.yaml:

  • ❌ noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >={{ python_min }} in the run section of your recipe. You may also want to check the upstream source for the package's Python compatibility.

For recipes/pyearthviz/recipe.yaml:

  • ℹ️ Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.
  • ℹ️ 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 the pin python ${{ python_min }}.* for the python entry.
    • For the run section of the recipe, you should usually use the pin python >=${{ python_min }} for the python entry.
    • For the tests[].python.python_version or tests[].requirements.run section of the recipe, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or 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).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21159970986. Examine the logs at this URL for more detail.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request adds a new conda recipe for pyearthviz, a lightweight Python package for 2D visualization and plotting of geospatial and Earth science data.

Changes:

  • Added conda-forge recipe for pyearthviz version 0.1.0
  • Configured as a noarch Python package with dependencies including numpy, gdal, matplotlib, cartopy, scipy, statsmodels, pandas, and pyearth
  • Included basic import tests and pip check validation

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +11 to +12
git: https://github.com/changliao1025/pyearthviz
rev: main
Copy link

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

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

The recipe is using a git repository as the source instead of a tarball. According to conda-forge best practices and the PR checklist, packages should be built from tarballs (url) rather than repos (git_url). Please update the source section to use a tarball from PyPI or a GitHub release tarball instead of cloning the repository directly.

Suggested change
git: https://github.com/changliao1025/pyearthviz
rev: main
url: https://pypi.io/packages/source/p/pyearthviz/pyearthviz-${{ version }}.tar.gz

Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Contributor

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

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jan 20, 2026

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/pyearthviz/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/pyearthviz/recipe.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 the pin python ${{ python_min }}.* for the python entry.
    • For the tests[].python.python_version or tests[].requirements.run section of the recipe, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or 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).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21161198480. Examine the logs at this URL for more detail.

@changliao1025
Copy link
Contributor Author

I am the author of this package, and I am willing to be listed here.
This package is part of the PyEarthSuite, which includes several Python package to assist Earth science data operation, visualization, etc. This package, particularly, is the core 2D visualization component.

@changliao1025
Copy link
Contributor Author

changliao1025 commented Jan 20, 2026

@conda-forge/help-python , the package is ready for review, thank you.

@github-actions
Copy link
Contributor

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

@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/pyearthviz/recipe.yaml) and found it was in an excellent condition.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants