load_setup_py_data() support

From some evaluation of boa, my thoughts are a) it’s wildly faster than conda-build, and b) we should be able to, and would love to, switch to it for most/all of our packages. Unfortunately, as it stands, that would currently be blocked in many cases by the lack of support for load_setup_py_data() (docs) or equivalent.

Is this something that you would be open to supporting in some form? I think it would also require some looping and maybe conditional support along the lines of what you outline in https://github.com/mamba-org/boa/issues/191#issuecomment-935540102

I think that the support for providing the data could be lifted directly from conda-build here. I’d be happy to provide a PR for that, but adding other templating constructs would presumably be a bit more involved.

[wolfv]

@dhirschfeld right, that’s exactly the kind of “recursive” chicken - and - egg situation that I would love to avoid.

Ideally instead of reading a setup.py, one would specify dependencies in a toml file or similar static metadata file and generate the boa and pypi “recipes” from that.

Or, you coudl use the setup.py file to simply parse the dependencies out of the boa recipe (since it’s pure yaml it’s straightforward!)

[dhirschfeld]

Ideally instead of reading a setup.py, one would specify dependencies in a toml file or similar static metadata file and generate the boa and pypi “recipes” from that.

It seems this functionality is now part of conda-build as load_file_data:

• https://docs.conda.io/projects/conda-build/en/stable/resources/define-metadata.html#loading-data-from-other-files

Added in https://github.com/conda/conda-build/pull/4480

@wolfv - is it planned to support load_file_data? If not, would that be a reasonable feature request?