search

conda-forge / conda-smithy

The tool for managing conda-forge feedstocks.
https://conda-forge.org/
BSD 3-Clause "New" or "Revised" License
147 stars 176 forks source link

How to force conda-smithy to generate configs for Python 3.8? #1212

Open mrakitin opened 4 years ago

mrakitin commented 4 years ago

For https://github.com/nsls-ii-forge feedstock, we'd like to start building arch packages for Python 3.8. Is there an easy way to force conda-smithy to generate the corresponding azure config entries? Thank you.

isuruf commented 4 years ago

You can use something like https://github.com/conda-forge/numpy-feedstock/blob/master/.ci_support/migrations/python38.yaml Or you can edit https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/conda_build_config.yaml for your organization

mrakitin commented 4 years ago

Thanks for the reply, @isuruf!

I tried the second proposed solution by modifying, e.g. https://github.com/nsls-ii-forge/analysis-feedstock/blob/master/recipe/conda_build_config.yaml, but event with a single python=3.8 version it was throwing the error:

...
  File "/Users/mrakitin/miniconda3/envs/conda-smithy/lib/python3.7/site-packages/conda_smithy/configure_feedstock.py", line 564, in _render_ci_provider
    os.path.join(forge_dir, "recipe"), config=config
  File "/Users/mrakitin/miniconda3/envs/conda-smithy/lib/python3.7/site-packages/conda_build/variants.py", line 520, in get_package_combined_spec
    combined_spec = combine_specs(specs, log_output=config.verbose)
  File "/Users/mrakitin/miniconda3/envs/conda-smithy/lib/python3.7/site-packages/conda_build/variants.py", line 277, in combine_specs
    log_output=log_output)
  File "/Users/mrakitin/miniconda3/envs/conda-smithy/lib/python3.7/site-packages/conda_build/variants.py", line 252, in _combine_spec_dictionaries
    spec_source))
ValueError: variant config in /Users/mrakitin/src/mrakitin/DAMA/nsls-ii-forge/all_feedstocks/analysis-feedstock/recipe/conda_build_config.yaml is ambiguous because it does not fully implement all zipped keys, or specifies a subspace that is not fully implemented.

Or did you mean to maintain the pinning package?