esmpy v8.4.1 noarch: python

[xylar]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

closes #69

[conda-forge-webservices[bot]]

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 (recipe) and found some lint.

Here's what I've got...

For recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The test section contained an unexpected subsection name. home is not a valid subsection name.
• The test section contained an unexpected subsection name. license is not a valid subsection name.
• The test section contained an unexpected subsection name. license_file is not a valid subsection name.
• The test section contained an unexpected subsection name. summary is not a valid subsection name.
• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[xylar]

@conda-forge-admin, please rerender

[conda-forge-webservices[bot]]

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 (recipe) and found some lint.

Here's what I've got...

For recipe:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[conda-forge-webservices[bot]]

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 (recipe) and found it was in an excellent condition.

[xylar]

@conda-forge-admin, please rerender

[xylar]

@zklaus, @ocefpaf and @rokuingh, I think this is working (though we won't know if it works for non-linux-64 architectures until we build a package).

I can confirm that mpi4py is optional: https://github.com/esmf-org/esmf/blob/v8.4.1/src/addon/esmpy/doc/install.rst

It also seems that one can install with esmf * nompi_* and test just fine with esmf * mpi_mpich_* so I think MPI isn't going to give us trouble.

As part of installation, we run the serial tests, and in the test phase we run MPI tests so I'm feeling like testing is about as thorough as it can reasonably be on on architecture.

Please let me know what you think.

[xylar]

@billsacks, would you or someone from the ESMF team be able to provide feedback on whether a noarch: python build for ESMPy is safe? We have the impression it is but want to be sure.

Also, it doesn't seem like @rokuingh is available at the moment. Is there someone else from the team that would be willing to join this (and the ESMF feedstock) as a maintainer?

[billsacks]

As you have found, @rokuingh 's availability is very limited right now. And, unfortunately, the ESMF team as a whole is currently at a reduced size; we are hoping to build it back up somewhat in the near future. I am trying to fill in for @rokuingh on critical ESMPy issues as part of my half-time work on ESMF, but I'm still very much in a learning phase myself. You can add me as a maintainer in order to keep me in the loop and act as a liaison between this community and the ESMF core team, but I can't promise a lot of time to this right now.

Regarding the noarch: python build: I don't know enough about this to give you a definite answer, and I think the same is true of others on the ESMF team. I'd say that, if it's passing your tests, then let's go ahead with it.

[xylar]

@conda-forge-admin, please rerender

[xylar]

@billsacks, we're all volunteers here so there's certainly no expectation of any time commitment. I've added you as a maintainer. We'll go ahead and give this a shot. @zklaus seems confident that this should work as expected and I trust his judgment.

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!