Open kmod opened 2 years ago
It's not a conda-smithy issue.
pin_run_as_build:
mpich: x.x
openmpi: x.x
msmpi: x.x
is not correct and a change in conda-smithy exposed this.
Thanks @kmod.
@isuruf I disagree, the pin_run_as_build
usage is legit, see the documented example and the conda-build source code.
Solution to issue cannot be found in the documentation.
Issue
mpy4py-feedstock is currently failing to rerender:
It looks like it's trying to interpret part of the config as a dict but it ends up being a single string. Here's the contents of the conda_build_config.yaml:
I checked some other feedstocks and they are written something like this:
which seems to be what conda-smithy is expecting. But @dalcinl and @leofang say that this used to work and is a regression in conda-smithy -- I couldn't find any documentation for conda-smithy indicating whether this is desired behavior or not, so I don't have a personal take on it.
Filed in the feedstock as https://github.com/conda-forge/mpi4py-feedstock/issues/53 but am moving it here at their request.
Installed packages
Environment info