How to specify optional packages?

[BastianZim]

Hi,

I have a question regarding the konoha package.

Here, the install options allow to install a couple of optional packages:

I recommend you to install konoha by pip install 'konoha[all]' or pip install 'konoha[all_with_integrations]'.
(all_with_integrations will install AllenNLP)

• Install konoha with a specific tokenizer: pip install 'konoha[(tokenizer_name)].
• Install konoha with a specific tokenizer and AllenNLP integration: pip install 'konoha[(tokenizer_name),allennlp].
• Install konoha with a specific tokenzier and remote file support: pip install 'konoha[(tokenizer_name),remote]'

Is it possible to do something like this with conda-forge recipes?

[beckermr]

You can use multiple outputs in the same recipe to build the kinds of variants above. See here: https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#outputs-section

[BastianZim]

Thank you, will do!

[croth1]

For future reference, here's an example for how @melund handled optional dependencies in the seaborn package: conda-forge/seaborn-feedstock#19!

[BastianZim]

That's really helpful, thank you!

Just to confirm, this line:

- {{ pin_subpackage('seaborn-base', max_pin="x.x.x.x") }}

just specifies that the base package should be included at the same version, correct? Am I correct in assuming that I could just copy/ paste that?

[beckermr]

You should check the conda-build docs. Depending on invocation this jinja2 statement can do a variety of things.

[BastianZim]

Thanks, will do!

[croth1]

In this case, if you are on seaborn-0.11.1, - {{ pin_subpackage('seaborn-base', max_pin="x.x.x.x") }} gets translated into following dependency:seaborn-base >=0.11.1,<0.11.2.0a0, I guess for conventional versioning, this should probably work for you as well. Due to the 4 x in x.x.x.x, I would have somehow expected it to result in seaborn-base >=0.11.1,<0.11.1.1a0, maybe @isuruf knows how this magic works?

[BastianZim]

Ok yeah, I found the following in the docs: https://docs.conda.io/projects/conda-build/en/latest/resources/variants.html#pinning-expressions and https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#export-runtime-requirements
So I probably should just see how many minor versions my package has and then translate that into the necessary amount of x.