Suggestion: add noarch

[regro-cf-autotick-bot]

I think this feedstock could be built with noarch. This means that the package only needs to be built once, drastically reducing CI usage. See herefor more information about building noarch packages.Before merging this PR make sure: Notes and instructions for merging this PR:

• [] No compiled extensions
• [] No post-link or pre-link or pre-unlink scripts
• [] No OS specific build scripts
• [] No python version specific requirements
• [] No skips except for python version. (If the recipe is py3 only, remove skip statement and add version constraint on python)
• [] 2to3 is not used
• [] Scripts argument in setup.py is not used
• [] If entrypoints are in setup.py, they are listed in meta.yaml
• [] No activate scripts
• [] Not a dependency of conda1. If any items in the above checklist are not satisfied, please close this PR. Do not merge.2. Please merge the PR only after the tests have passed.
  3. Feel free to push to the bot's branch to update this PR if needed. _{This PR was created by the cf-regro-autotick-bot. The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.}

Finally, feel free to drop us a line if there are any issues!

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

[marscher]

this pkg is not noarch, because it has compiled extensions. @conda-forge-coordinator: this could be a case for a false positive.