staged-recipes | submit conda recipes before they become fully fledged conda

by conda-forge Python Version: Current License: BSD-3-Clause

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | staged-recipes Summary

staged-recipes is a Python library. staged-recipes has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However staged-recipes build file is not available. You can download it from GitHub.

This repo is a holding area for recipes destined for a conda-forge feedstock repo. To find out more about conda-forge, see

Support

Quality

Security

License

Reuse

Support

staged-recipes has a low active ecosystem.

It has 634 star(s) with 4047 fork(s). There are 24 watchers for this library.

It had no major release in the last 6 months.

There are 186 open issues and 676 have been closed. On average issues are closed in 323 days. There are 397 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of staged-recipes is current.

Quality

staged-recipes has 0 bugs and 0 code smells.

Security

staged-recipes has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

staged-recipes code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

staged-recipes is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

staged-recipes releases are not available. You will need to build from source code and install.

staged-recipes has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

It has 81 lines of code, 5 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed staged-recipes and discovered the below as its top functions. This is intended to give you an instant insight into staged-recipes implemented functionality, and help decide if they suit your requirements.

Build all recipes
Build a list of recipes
Get the configuration for a given arch
Return the host platform
Expand a given run
Verify if config is valid
Prints information about the GitHub API rate limiting
Set the default branch for feedstocks
Return the topological order of a graph
Reorder test nodes in graph
Setup the environment
Check that all recipes in the correct directory are in the correct directory
Return the default branch name
Check if a recipe is build

Get all kandi verified functions for this library.

staged-recipes Key Features

No Key Features are available at this moment for staged-recipes.

staged-recipes Examples and Code Snippets

No Code Snippets are available at this moment for staged-recipes.

Community Discussions

Trending Discussions on staged-recipes

Can this problem be implemented in parallel in Cython with OpenMP?

How to add a proper 'meta.yaml' recipe file for creating a conda-forge package distribution? Particularly `test` section in recipe file?

Conda-forge package build fails with: CC required but not found even though compiler is added

conda-forge recipe for python package with a fortran extension not working on appveyor

yaml file for conda packages update programmatically

QUESTION

Can this problem be implemented in parallel in Cython with OpenMP?

Asked 2019-Dec-10 at 13:51

I have parallalised some Cython code with OpenMP. Once in a while, the code computes wrong results.

I created a nearly minimal working example of my problem. "Nearly", because the frequency of the wrong results seem to depend on even the tiniest changes in code, thus, e.g. I kept the function pointers in.

The Cython code is

...

ANSWER

Answered 2019-Dec-09 at 15:20

Contrary to their name, variogram_local and counts_local are not actually local. They are shared and all threads mess around with them in parallel, hence the undefined result.

Note that you don't actually share any work. It's just all threads doing the same thing - the whole serial task.

A somewhat sensible parallel version would look more like this:

Source https://stackoverflow.com/questions/59250916

QUESTION

How to add a proper 'meta.yaml' recipe file for creating a conda-forge package distribution? Particularly `test` section in recipe file?

Asked 2019-Jul-16 at 09:07

I'm trying to have conda-forge host a python package I've created which is already on PyPI: https://pypi.org/project/ludoSim-jaib1/

I've read the conda-forge documentation on contributing packages here and the conda documentation on defining metadata via a meta.yaml recipe file here

My submitted pull request to the conda-forge/staged-recipes repo is here. My meta.yaml file can be found in that pull request, but I'll post it in text here as well:

...

ANSWER

Answered 2019-Jul-16 at 09:07

The following document is the canonical reference for everything I repeat below:

https://docs.conda.io/projects/conda-build/en/stable/resources/define-metadata.html#test-section

When creating conda recipes, there are (AFAIK) three ways to define tests that will get executed:

create run_test.[py,pl,sh,bat] in the recipe directory (this is automatically discovered by conda-build
include test/imports to test that python modules can be imported
include test/commands to run arbitrary shell commands

These can be supplemented by source_files, requires, and a number of other keys to format a test environment properly. I think, given your problem description:

for my package, I want to run a test script which exists in my package, depends on the pytest package, and which needs to be run in the parent directory of the location my package is located in

you probably want something like this:

Source https://stackoverflow.com/questions/57031437

QUESTION

Conda-forge package build fails with: CC required but not found even though compiler is added

Asked 2019-Jun-10 at 06:40

I want to create a conda-forge package for https://github.com/uber/h3-py and have followed the instructions of https://conda-forge.org/docs/maintainer/adding_pkgs.html#staging-test-locally.

The recipe can be found here: https://github.com/geoHeil/staged-recipes/blob/h3-py/recipes/h3/meta.yaml

When trying to execute a local build using:

...

ANSWER

Answered 2019-Jun-10 at 06:40

I had to create a custom build.sh file:

where instead of relying on some $CC, cmake automatically uses the right environment. https://github.com/conda-forge/staged-recipes/pull/8467/files

Source https://stackoverflow.com/questions/56341092

QUESTION

conda-forge recipe for python package with a fortran extension not working on appveyor

Asked 2018-Nov-10 at 03:05

I am trying to get a conda-build recipe to pass all the CI tests on conda-forge/staged-recipes. Here is a link to the pull request The python package has a fortran extension and uses numpy.distutils in the setup.py to build the extension. Circle CI for Linux, Travis-CI for OSX pass, but I cannot get Appveyor for Windows to work with the conda-build recipe.

When using Miniconda for the Appveyor build for Windows and Travis CI build for OSX and Linux for the package repo everything works and the tests pass. I can also get the conda-build recipe to work locally on Windows and Linux, but as you can see from the pull request to conda-forge the tests do not pass for Windows using Appveyor.

The import test fails to load the fortran extension with ImportError: DLL load failed: The specified module cannot be found. The extension module is copied to the site-packages directory, copying build\lib.win-amd64-3.6\timml\besselaesnew.cp36-win_amd64.pyd C:\bld\timml_1541596078787\_h_env\Lib\site-packages\timml, so I am stumped why it is not being found. I read about the differences between .pyd and dll, and tried --compiler=mingw32 instead of --compiler=msvc as mentioned here. That still didn't work. I also added zlib to the host and run section, after reading this and that didn't help.

Any tips to get a conda-build recipe for python package with a fortran extension working on Appveyor would be greatly appreciated. The compiler args in the setup.py file for windows is copied below in case that matters.

if os.name == "nt": compile_args = ["-static-libgcc", "-Wall", "-shared"]

...

ANSWER

Answered 2018-Nov-10 at 03:05

The issue was with the difference between dll and .pyd files and the compiler specification. After looking at the conda-forge-pinning conda_build_config.yaml, the way to choose mingw instead of msvc is:

Source https://stackoverflow.com/questions/53196129

QUESTION

yaml file for conda packages update programmatically

Asked 2017-Oct-12 at 06:29

I have a python script that would like to read a set of conda recipes and update them with some information (e.g. file: https://github.com/williamjamir/staged-recipes/blob/850760fb63c0fc000b95ac27680ec018fa94dcb7/recipes/pyexcel-ezodf/meta.yaml) :

I'm using this:

...

ANSWER

Answered 2017-Oct-12 at 06:29

The dump() method for a YAML instance doesn't take the parameters you provide (allow_unicode=True, explicit_start=True). As you didn't provide a full working program, I can only guess that you (also) do a import ruamel.yaml as yaml (or even import yaml).

The conversion done by the jinja2 plugin, that deals with the standard jinja2 template syntax (that normally is processed before parsing with the YAML parser) needs to be done while loading and while dumping. So you need to use the same YAML(typ='jinja2') instance to do so:

Source https://stackoverflow.com/questions/46677139

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install staged-recipes

Fork this repository.
Make a new folder in recipes for your package. Look at the example recipe, our documentation and the FAQ for help.
Open a pull request. Building of your package will be tested on Windows, Mac and Linux.
When your pull request is merged a new repository, called a feedstock, will be created in the github conda-forge organization, and build/upload of your package will automatically be triggered. Once complete, the package is available on conda-forge.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: