Adding hazelbean

[phargogh]

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.
• 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/hazelbean/meta.yaml) and found some lint.

Here's what I've got...

For recipes/hazelbean/meta.yaml:

• The following maintainers have not yet confirmed that they are willing to be listed here: jandrewjohnson. Please ask them to comment on this PR if they are.

For recipes/hazelbean/meta.yaml:

• No valid build backend found for Python recipe for package hazelbean using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[phargogh]

I confirm that I am willing to be a recipe maintainer. @jandrewjohnson could you confirm that you are willing to be a maintainer as well? Please comment here if so.

[jandrewjohnson]

I confirm that I am willing to be a recipe maintainer.

[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/hazelbean/meta.yaml) and found it was in an excellent condition.

[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/hazelbean/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/hazelbean/meta.yaml:

• No valid build backend found for Python recipe for package hazelbean using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[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/hazelbean/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

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/hazelbean/meta.yaml) and found some lint.

Here's what I've got...

For recipes/hazelbean/meta.yaml:

• requirements: run: python>=3.6 must contain a space between the name and the pin, i.e. python >=3.6
• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[conda-forge-admin]

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/hazelbean/meta.yaml) and found it was in an excellent condition.

[phargogh]

Ok, I think this is ready for review! @conda-forge/help-python

[ocefpaf]

This file is in the tarball. You don't need to re-add it here.

[conda-forge-admin]

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/hazelbean/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipes/hazelbean/meta.yaml:

• Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

[conda-forge-admin]

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/hazelbean/meta.yaml) and found it was in an excellent condition.

[phargogh]

@ocefpaf you are very right, the dependencies were a combination of actual dependencies and build tools, which were taken from the upstream package's documentation, but clearly this list was a bit larger than was needed for this package, specifically. Thanks for your review!

[ocefpaf]

Unless you do some code generation at run time, it is very likely that cython is not required to run this.

Suggested change

- Cython

[ocefpaf]

Ping

[phargogh]

Removed in dfab217

[ocefpaf]

Suggested change

- {{ stdlib("c") }}

[phargogh]

I just removed this and also libgcc in cef1607.

[ocefpaf]

Installing at runtime libgcc is not advised. It is very unlikely that you need this.

Suggested change

- libgcc

[phargogh]

I just removed this and stdlib(c) in cef1607. The builds were failing without including libgcc before, so I'm curious if removing both lines would result in a successful build.

[ocefpaf]

Can you check if you really need six? Are you still supporting Python 2 syntax with it?

Suggested change

- six

[phargogh]

While I agree with you that python2 support is no longer needed, a vendored version of a library within hazelbean does still use six, so it is, at this time, still a dependency.

[conda-forge-admin]

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/hazelbean/meta.yaml) and found some lint.

Here's what I've got...

For recipes/hazelbean/meta.yaml:

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

[conda-forge-admin]

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/hazelbean/meta.yaml) and found it was in an excellent condition.