How to programatically determine the build matrix of a feedstock
See original GitHub issueWhat is the best way to pull the conda-smithy
version used most recently from a feedstock?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Resources | Free Full-Text | Calculating MIPS 2.0 - MDPI
The official handbook applicable to products, services, and processes describes a MS Excel-based sequential approach for calculating MIPS. Today's computing ...
Read more >7 Quick and Easy Steps to Creating a Decision Matrix ... - Asana
1. Identify your alternatives ... Decision matrices are a helpful tool to decide the best option between a set of similar choices. Before...
Read more >Laser-Directed Energy Deposition Additive Manufacturing
Observation of oxides on 316L feedstock particle surfaces . ... it is programmatically much more complicated to construct the toolpath.
Read more >us department of energy - DOE Office of Science
to develop other chemical analysis tools that enable us to measure ... applications and sensor-driven environmental science, and the Array of Things and ......
Read more >Optimizing Scheduling and Blending Operations ... - MathWorks
MathWorks Matrix Menu ... MathWorks Matrix Menu ... on what we can make. And in this case, we actually know what the costs...
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 FreeTop 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
Top GitHub Comments
@ericdill As mentioned in https://github.com/conda-forge/conda-smithy/issues/168#issuecomment-219043880, if a conda-smithy update doesn’t actually change anything in the rendering, then this would still change the repo on an update, kicking off builds. I guess that could still be okay if conda-smithy detected this situation and added
[skip ci]
to the commit message…@CJ-Wright do you want the build matrix or do you want to check the contents of the
conda-forge
channels for packages that lack py36 support. It’s reasonably straightforward to search through the repodata.json on each of the channels for such information