Add recipe for ragna

[aktech]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there. ping @pmeier @pavithraes
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/ragna) and found some lint.

Here's what I've got...

For recipes/ragna:

• The home item is expected in the about section.
• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/ragna) and found some lint.

Here's what I've got...

For recipes/ragna:

• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/ragna) and found some lint.

Here's what I've got...

For recipes/ragna:

• requirements: run: huey >= 2.5.0 should not contain a space between relational operator and the version, i.e. huey >=2.5.0

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/ragna) and found it was in an excellent condition.

[aktech]

@pmeier The failure is:

Traceback (most recent call last):
...
    import huey.contrib.asyncio
ModuleNotFoundError: No module named 'huey.contrib.asyncio'

This is because the huey version installed in the CI is 2.1.3, where as this huey version doesn't have huey.contrib.asyncio module. The latest release of huey is not present on conda, unlike PyPi.

This is not worth fixing as it has been removed in the main branch (unreleased) ragna git: Quansight/ragna#205 So, it's better to wait for the next release of ragna on PyPi, before adding on conda-forge.