Bastian Zimmermann

Sometimes, the names in conda-forge are different than in PyPI. What this config.yaml does is it saves all of the differences and then when you run Grayskull on a package,...

The file already exists, it was just moved to here: https://github.com/conda-incubator/grayskull/blob/main/grayskull/strategy/config.yaml And yeah, GitHub search isn't always the best... You can use souschef but if you add the respective package...

I think the easiest solution is to check the folder where the output is placed in for already generated recipes (Although that doesn't work when outputting to the console). Maybe...

Not right now unfortunately, but I'll post here if I find something. It should be for all {{ rust }} recipes though.

> Manual run, submit each release Are you talking about submitting a new release or a new package? The former is done automatically by the conda-forge bots.

Yeah but we need to figure out what exactly the equivalent is because flit also has https://flit.pypa.io/en/latest/pyproject_toml.html#entry-points-sections Maybe https://flit.pypa.io/en/latest/pyproject_toml.html#scripts-section is `scripts` from setup.py? In that case it can't be noarch.

Oh yeah – missed that. Would make the most sense then, agreed.

That sounds good and yeah, I also disagree with the placeholder, just wasn't sure if that is documented behaviour or not. :)

> Also any ideas for best way to add dwave_networkx with out using pip like this: The package is called dwave-networkx on conda-forge.

I'm currently on my phone but I'll have a look in an hour or so.