Adding greybox

[config-i1]

Summary

• PyPI package greybox v1.0.0 — Python port of the R greybox package
• Toolbox for likelihood-based regression model building and forecasting:
  • Augmented Linear Model (ALM) supporting 26+ distributions
  • R-style formula parser
  • IC-based stepwise variable selection and model combination
  • Comprehensive forecast error measures
• License: LGPL-2.1-only
• Pure Python (noarch: python); no compiled extensions
• Not a dependency of any other conda-forge package at this time

Checklist

• Title of this PR is meaningful: "Adding greybox"
• License file is packaged (license_file: LICENSE)
• Source is from official source (PyPI tarball, not a fork)
• Package does not vendor other packages
• No static libraries are linked or shipped (pure Python)
• Build number is 0
• A tarball (url) is used, not git_url
• All dependencies are available on conda-forge (numpy, scipy, pandas, nlopt)
• GitHub user config-i1 listed as maintainer has confirmed willingness to maintain
• conda-forge documentation consulted before submitting

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

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

For recipes/greybox/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 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 test.requires section of the recipe, you should usually use the pin 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/22306762598. Examine the logs at this URL for more detail.}

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• .ci_support/osx64.yaml:
  • lints:
    • Do not edit files outside of the recipes/ directory.

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

[github-actions]

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