Skipping python 3.6 still creates CI job in multi-output recipe
See original GitHub issueIn https://github.com/conda-forge/modin-feedstock/pull/13, I updated skip: true # [py<37]
, since upstream isn’t compatible with 3.6 anymore.
While trying to turn this recipe into a multi-output version, rerendering cause the 3.6 CI jobs to reappear (even though the build is skipped, so CI should stay green).
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Skipping python 3.6 still creates CI job in multi-output recipe
In conda-forge/modin-feedstock#13, I updated skip: true # [py<37], since upstream isn't compatible with 3.6 anymore.
Read more >Changelog — Python 3.11.1 documentation
gh-95174: Python now skips missing socket functions and methods on WASI. WASI can only create sockets from existing fd / accept and has...
Read more >Your First Machine Learning Project in Python Step-By-Step
Load a dataset and understand it's structure using statistical summaries and data visualization. Create 6 machine learning models, pick the best ...
Read more >Nextflow training
When creating a Conda environment with a YAML recipe file, Nextflow automatically downloads the required dependencies, builds the environment and activates it.
Read more >Release Notes - Numba - PyData |
Lucio Fernandez-Arjona added mypy to CI and started adding type annotations to the code base in ... The next release (0.48.0) will be...
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
conda-smithy performs re-rendering by having conda-build parse the recipe and run conda render (a feature of conda-build). So yes it is a conda-build issue
OK, thx