continuumio / anaconda-verify Goto Github PK

This project is very well self-contained and doesn't seem to depend on anything but itself. It would be awesome if you'd publish it to PyPI. This isn't me trolling I promise - I work on a tool developer-oriented project that gets published to PyPI and bioconda and I'd love to cleanly reuse this as a library to assist in conda recipe development. I'll do some hacking for now - but the cleanly part would be nice.

Thanks!

I'm running conda ver. 4.1.12 on a Mac Pro running Mac OS X Sierra (10.12.1). I was attempting to install the package astroplan. I got error messages saying that the SSL module was not available.

Now this is the first time running under Mac OS X Sierra that I got SSL verification error messages. I did check the settings in my .condarc file and found that ssl_verify: true.

I've attached a file containing the error message and the reults of using the conda info -a command.

Please advise.

Sam Dupree.

SSL_verificatin_error_conda.txt

It appears that it is not valid for a recipe to use Jinja according to this code. One of our conda-forge contributors, @ngoldbaum, pointed this out to us.

We find it very handy to use Jinja so that we can avoid copy-pasta with versions and the like. Thus we are able to set them in one place and use {{ version }} elsewhere. This keeps the maintenance burden on updates low. It also avoids silly mistakes like bumping the version number and using the same source. Further in light of changes to PyPI URLs, we have found ourselves needing the name to be used in Jinja templates so as to handle the current redirect URLs.

While we are using Jinja, it is hardly dynamic and a single pass of conda render can fill this out without needing to go to external source (though maybe the NumPy and/or Python versions may be needed).

Is there some reason to consider this usage unacceptable?

cc @pelson @ocefpaf @msarahan

When using a meta.yaml with a "source from a local path" as described at http://conda.pydata.org/docs/building/meta-yaml.html#source-from-a-local-path , anaconda-verify complains about

RecipeError: in section 'source': unknown key 'path'

If anaconda-verify is only meant to be used for recipes that live separately from the source code (and therefore use URLs), this should be stated somewhere.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>anaconda/renovate-config)

After taking an existing recipe and running conda rerender on it (with the needed NumPy version), I generated a new static meta.yaml file that does not have Jinja so as to avoid this issue ( #2 ). When running anaconda-verify on this, I run into a new issue. It appears the extra section is unsupported. 😕

==> recipe/ <==
RecipeError: Unknown section: extra

cc @pelson @ocefpaf @msarahan