-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add pyearthviz3d to conda #31962
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
base: main
Are you sure you want to change the base?
Add pyearthviz3d to conda #31962
Conversation
|
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
|
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 ( I do have some suggestions for making it better though... For recipes/pyearthviz3d/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21162052720. Examine the logs at this URL for more detail. |
There was a problem hiding this 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-forge recipe for pyearthviz3d, a Python package for 3D visualization of geospatial and Earth science data. The recipe uses the new YAML-based format (recipe.yaml) introduced by CEP 13.
Changes:
- Adds conda recipe configuration for pyearthviz3d version 0.1.0
- Configures the package as noarch Python with dependencies including numpy, geovista, pyvista, gdal, and pyearth
- Sets up basic import tests and package metadata
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| git: https://github.com/changliao1025/pyearthviz3d | ||
| rev: main |
Copilot
AI
Jan 20, 2026
There was a problem hiding this comment.
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 guidelines, recipes should build from tarballs (url) rather than git repositories. This is mentioned in the PR checklist and is a requirement for conda-forge recipes. Please use a tarball from a GitHub release or PyPI instead. For example, you could use the PyPI source tarball or create a GitHub release and use that tarball URL.
| git: https://github.com/changliao1025/pyearthviz3d | |
| rev: main | |
| url: https://github.com/changliao1025/pyearthviz3d/archive/refs/tags/${{ version }}.tar.gz |
| source: | ||
| git: https://github.com/changliao1025/pyearthviz3d | ||
| rev: main |
Copilot
AI
Jan 20, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using a tarball source (url) instead of git, you must include a sha256 checksum for the source file. This ensures reproducibility and verifies the integrity of the downloaded source. You can obtain the sha256 hash using openssl sha256 on the downloaded tarball file.
|
@conda-forge/help-python , pyearthviz3d is ready for review, thank you. |
Checklist
url) rather than a repo (e.g.git_url) is used in your recipe (see here for more details).