Add ncountr

[princello]

Description

ncountr is the first Python package for end-to-end Nanostring nCounter data analysis. It parses RCC files, runs QC, normalizes counts, tests for differential expression, and scores gene sets — all from a single config file or Python API.

• Home: https://github.com/princello/ncountr
• PyPI: https://pypi.org/project/ncountr/0.1.0/
• Docs: https://ncountr.readthedocs.io
• License: MIT
• sha256: 4c0416871eda8326fb5e59f9ce7afb7ea1157e6a9226f8cd1995b6b09c00ac70 (included in recipe)

Checklist

• Source archive is available on PyPI
• sha256 hash is set in meta.yaml
• License file is included (MIT)
• Tests pass (ncountr --version, ncountr --help, imports)
• noarch: python build
• Recipe maintainer listed (princello)

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

Here's what I've got...

For recipes/ncountr/meta.yaml:

• ❌ When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

For recipes/ncountr/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).

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

[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 just wanted to let you know that I linted all conda-recipes in your PR (recipes/ncountr/meta.yaml) and found it was in an excellent condition.

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

For recipes/ncountr/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).

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