Add cmeutils

[jennyfothergill]

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.
• 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.

[conda-forge-linter]

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

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

For recipes/cmeutils:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[jennyfothergill]

@chrisjonesBSU @erjank comment here if you're OK with being a maintainer for cmeutils on conda-forge

[chrisjonesBSU]

@chrisjonesBSU @erjank comment here if you're OK with being a maintainer for cmeutils on conda-forge

I am Ok with being a maintainer for cmeutils on coda-forge

[conda-forge-linter]

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

[jennyfothergill]

@conda-forge/staged-recipes this PR is ready for review

[synapticarbors]

Is cython required? I don't see it in the source code. Also it seems like pip shouldn't be a run time requirement either.

[jennyfothergill]

cython is not required, but the build for 27f2761 was failing because freud was not pulling cython. I will make an issue on freud and remove pip.

[bdice]

It should be safe to remove cython from the runtime requirements of this package.

Cython was mistakenly listed in install_requires for freud, meaning that pip check was searching for Cython as a runtime requirement. It is only a build-time requirement, which is correctly listed in the freud feedstock but not in freud's setup.py. This caused pip check to fail. This PR will fix the upstream for freud's next release: glotzerlab/freud#938 In the meantime, I would skip the pip check test. Thank you for the bug discovery!