Make noarch

[mcflugen]

Checklist

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

This pull request makes cfunits a noarch package.

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

[mcflugen]

@ocefpaf I would like to use this package on Windows (well, not me personally - my Windows people would like to use it). This pull request was initially intended to make cfunits build on Windows but I noticed that, I think, it should work just fine as a noarch package. I believe all of its dependencies run on Windows so that should be fine.

Does that make sense?

[ocefpaf]

Does that make sense?

If the package does not have compiled extensions then it does makes sense. The setup.py imports Extension in the first line but I do not believe it is used. Maybe it is better to ask someone that is more familiar with the source code before merging this.

[mcflugen]

@ocefpaf Thanks. I asked you because you seemed to be the biggest contributor to the feedstock. I filed an issue with the cfunits developers over at Bitbucket. We'll see what they say.

@cehbrecht, I'm not sure what your connection is to cfunits but you're listed as a maintainer of the feedstock. Do you have any thoughts?

[ocefpaf]

@ocefpaf Thanks. I asked you because you seemed to be the biggest contributor to the feedstock.

No problem. But sometimes I package so many things and I don't really know the source code in depth.

I filed an issue with the cfunits developers over at Bitbucket. We'll see what they say.

Thanks! If we don't get an answer we can try to merge, test, and if things are broken revert it later.

[mcflugen]

@ocefpaf It's just about been a week and I've not heard back. What do you think, should we go ahead and merge?

[ocefpaf]

@ocefpaf It's just about been a week and I've not heard back. What do you think, should we go ahead and merge?

Let's give it a try, if it breaks the package we can remove it later.