Add opengeotech recipe

[jadinata]

Adding opengeotech

This PR adds a recipe for opengeotech, a Python package that provides functions for geotechnical engineering calculations.

About the package

Opengeotech is designed to simplify geotechnical engineering workflows with Python. The current version (0.1.0) includes fundamental functionality like effective stress calculations, with plans to expand to cover more geotechnical engineering applications in future releases.

Checklist

• Title of this PR is meaningful: "Add opengeotech"
• Package is already on PyPI
• License is included (MIT)
• Recipe includes basic tests
• Used the noarch: python when appropriate
• Added appropriate Python version constraints
• SHA256 hash verified and correct

Community information

This package is part of the OpenGeotechnical initiative, which aims to provide open-source tools for geotechnical engineers and researchers.

Additional notes

The package has minimal dependencies, requiring only Python 3.6+.

[github-actions]

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

[conda-forge-admin]

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/opengeotech/meta.yaml) and found some lint.

Here's what I've got...

For recipes/opengeotech/meta.yaml:

• ❌ There are too few lines. There should be one empty line at the end of the file.

For recipes/opengeotech/meta.yaml:

• ℹ️ No valid build backend found for Python recipe for package opengeotech using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of 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.

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

[conda-forge-admin]

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

[conda-forge-admin]

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

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

For recipes/opengeotech/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of 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).

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

[jadinata]

Hi @conda-forge/help-python, could you please review this PR when you have a chance? Thanks!

[jadinata]

Hi @ocefpaf , I noticed you've recently reviewed a PR—would you mind taking a look at mine when you have a moment? I'd really appreciate your time and any feedback you might have. Thanks so much in advance!

[ocefpaf]

No need to ping me directly. The whole team was pinged when you addressed the Python reviewers, including me.

[ocefpaf]

Please address #29479 (comment)

[conda-forge-admin]

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