Add stdio-mgr recipe to conda-forge

[anjos]

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.

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

[anjos]

@conda-forge/help-python ping

[ocefpaf]

• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.

@bskinn can you comment here saying you are OK being a maintainer for this feedstock?

[bskinn]

Confirmed, ok here.

I may need some hand holding, I'm new to conda-forge recipe maintenance, but I'm interested to learn.

[anjos]

@bskinn: without the attrs package on the host, it does not build. I'll add it back. See logs here.

[bskinn]

@anjos -- yeah, I need to update my setup.py here so that it extracts the version number without importing the whole package. One of many overdue points of maintenance.

[anjos]

No worries, @bskinn - we can iterate on this more easily now.