remove conda recipe. allow python setup.py test to run correctly

[loriab]

• removed the conda recipe b/c (a) I don't think it gets much populated by the cookiecutter, (b) isn't used in CI, and (c) makes a third place ppl need to specify deps and versions
• some changes that allow pytest via python setup.py test. see make python setup.py test work QCElemental#39

[dgasmith]

I like this as it simplifies the cognitive overhead and the conda-forge solution seems to be working as well. Will keep this open for awhile, especially for @Lnaden to weigh in.

[dgasmith]

Overall looks good, merging!

[jchodera]

the conda-forge solution seems to be working as well.

What is "the conda-forge solution"?

[dgasmith]

Deploying to conda-forge rather than your own channel. We have moved many projects there and folks have had many less hitches than deploying your own. It is also managed, so much better than custom channels.

[jchodera]

Totally agree that conda-forge is the way to go if projects are free of dependencies they don't provide.

I was just wondering how the cookiecutter specifically aided people in setting up conda-forge recipes now that the development recipe is no longer used.

[dgasmith]

We point them to Bioconda, Omnia, and the Conda docs. We had a lot of complaints trying to figure out what the meta.yaml file is for which catalyzed their removal. From our feedback and teaching this cookiecutter to about 150 students, outside of the Bioconda/Omnia community we have not had a use case where conda-forge does not work. So it seem that the non-cf solution is an extreme edge case that can be better handled by the folks running the non-cf channels.