Add recipe for idaes-pse

[lbianchi-lbl]

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

Here's what I've got...

For recipes/idaes-pse/meta.yaml:

• ❌ There are too few lines. There should be one empty line at the end of the file.
• ❌ requirements: host: click>=8 must contain a space between the name and the pin, i.e. click >=8
• ❌ requirements: host: numpy>=1.17 must contain a space between the name and the pin, i.e. numpy >=1.17
• ❌ requirements: host: pyomo>=6.8.0 must contain a space between the name and the pin, i.e. pyomo >=6.8.0
• ❌ requirements: run: click>=8 must contain a space between the name and the pin, i.e. click >=8
• ❌ requirements: run: numpy>=1.17 must contain a space between the name and the pin, i.e. numpy >=1.17
• ❌ requirements: run: pyomo>=6.8.0 must contain a space between the name and the pin, i.e. pyomo >=6.8.0
• ❌ 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.

For recipes/idaes-pse/meta.yaml:

• ℹ️ Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.
• ℹ️ No valid build backend found for Python recipe for package idaes-pse 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.
• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).
• ℹ️ License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found 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/idaes-pse/meta.yaml) and found it was in an excellent condition.

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

For recipes/idaes-pse/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

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

[lbianchi-lbl]

@conda-forge-admin please ping team @conda-forge/help-python

This is ready for review.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[xhochy]

Not needed anymore.

Suggested change

{% set python_min = "3.9" %}

[xhochy]

Suggested change

# idaes_pse/meta.yaml

[xhochy]

Here are way too much things listed. There should only be the things that are required to build the package, e.g. setuptools.

[lbianchi-lbl]

Thanks, I see what you mean. Done in ed160f7

[xhochy]

Suggested change

	commands:
	commands:
	- pip check

[lbianchi-lbl]

Done in f98fa23

[xhochy]

Suggested change

	requires:
	requires:
	- pip

[lbianchi-lbl]

Done in b0f4070

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

Here's what I've got...

For recipes/idaes-pse/meta.yaml:

• ❌ The recipe is not parsable by any of the known recipe parsers (['conda-forge-tick (the bot)', 'conda-recipe-manager', 'conda-souschef (grayskull)']). Please check the logs for more information and ensure your recipe can be parsed.

For recipes/idaes-pse/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-forge-tick (the bot). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11961677680. Examine the logs at this URL for more detail.}

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

[lbianchi-lbl]

Thanks a lot for the feedback @xhochy. I believe I have addressed all your comments, but let me know if that's not the case.