Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
conflict with conda_build_config.yaml and conda-forge.yml
See original GitHub issueBy default, conda-smithy takes the conda_build_config.yaml in the miniconda path. In this file, we have
channel_targets:
- conda-forge main
Even if you add in conda-forge.yml the lines
channels:
targets:
- [gouarin, main]
it takes the target channel defined in conda_build_config.yaml. If I add my own conda_build_config.yaml in my recipe with the lines
channel_targets:
- gouarin main
it works.
But I think that the configuration sets in the conda-forge.yaml shoud take the priority.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
conda-build Documentation
We will specify building against Python 3.7 and 3.5 using a conda-build config. Add the following to your conda_build_config.yaml: python:.
Read more >Additional Considerations — bob.devtools 5.4.1b0 ...
The CI system is based on conda recipes to build the package. The recipes are located in the conda/meta.yaml ; The template meta.yaml...
Read more >sklearndf Changelog - pyup.io
conda install -c conda-forge -c bcg_gamma sklearndf. Changes: ... BUILD: do some pip builds from source to prevent numpy binary API clash (216)...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
PRs are welcome. Note that the README still uses the conda-forge.yml so that should be fixed as well.
Just ran into this with a pre-release of python 3.8.0. Not a big deal since I can relabel the packages after they get uploaded to Anaconda Cloud.
My vote would be to remove this feature entirely from
conda-forge.yamland leave it this functionality toconda_build_config.yaml