Add pymer4 to conda-forge

[ejolly]

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.

Please note that this PR subsumes #22346 using the most recent version of pymer4 on pip and anaconda cloud. I'm grateful to @leej3 getting that started, but I opened this new PR so I can maintain the staged-recipes fork for future maintenance as I'm the core-developer for pymer4.

The meta.yaml file was built using conda-render to parse the template variables of the meta.yaml that successfully supports anaconda cloud builds.

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

Here's what I've got...

For recipes/pymer4/meta.yaml:

• ❌ The recipe must have a build/number section.
• ❌ license_file entry is missing, but is required.
• ❌ The extra section contained an unexpected subsection name. copy_test_source_files is not a valid subsection name.
• ❌ The extra section contained an unexpected subsection name. final is not a valid subsection name.

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

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

Here's what I've got...

For recipes/pymer4/meta.yaml:

• ❌ The recipe must have some tests.
• ❌ The requirements section contained an unexpected subsection name. test is not a valid subsection name.

For recipes/pymer4/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • 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/15174702380. 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/pymer4/meta.yaml) and found it was in an excellent condition.

[ejolly]

@conda-forge-admin The noarch python build of the package is intentional and does not officially support windows given limitations of the cross-language dependency of R, Python, and the rpy2 translation layer.

Is it possible to skip the win_64 build and checks? Otherwise I believe everything else seems up to spec?
Tagging @saraedum as they were responsive to #22346

[stale]

Hi friend!

We really, really, really appreciate that you have taken the time to make a PR on conda-forge/staged-recipes! conda-forge only exists because people like you donate their time to build and maintain conda recipes for use by the community.

In an effort to maintain this repository and increase the signal-to-noise for open PRs, the maintainers of staged-recipes close excessively old PRs after six months. This PR will remain open for another month, and then will be closed.

If you'd like to keep it open, please comment/push and we will be happy to oblige! Note that very old PRs will likely need to be rebased on main so that they can be rebuilt with the most recent CI scripts. If you have any trouble, or we missed reviewing this PR in the first place (sorry!), feel free to ping the team using a special command in a comment on the PR to get the attention of the staged-recipes team.

Cheers and thank you for contributing to this community effort!

[ejolly]

@conda-forge-admin Please ping the team regarding my previous question

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/the and so here I am doing that.