Add TidalPy

[jrenaud90]

Opening this PR for the TidalPy python package which has components written in Cython. Tests are passing on various systems via GitHub actions. We will see if they pass in conda-forge's CI!

Thanks for all you do.

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.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

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

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

For recipes/TidalPy/meta.yaml:

• ℹ️ Recipes should usually depend on astropy-base as opposed to astropy. astropy-base only has the required dependancies whereas astropy now has all optional dependancies as well.

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

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

Here's what I've got...

For recipes/TidalPy/meta.yaml:

• ❌ requirements: run: ipympl>=0.9.6, <0.10.0 must contain a space between the name and the pin, i.e. ipympl >=0.9.6,<0.10.0

For recipes/TidalPy/meta.yaml:

• ℹ️ Recipes should usually depend on astropy-base as opposed to astropy. astropy-base only has the required dependancies whereas astropy now has all optional dependancies as well.
• ℹ️ Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12664348873. 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/TidalPy/meta.yaml) and found it was in an excellent condition.

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

For recipes/TidalPy/meta.yaml:

• ℹ️ Recipes should usually depend on astropy-base as opposed to astropy. astropy-base only has the required dependancies whereas astropy now has all optional dependancies as well.
• ℹ️ Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12664382061. 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/TidalPy/meta.yaml) and found it was in an excellent condition.

[jrenaud90]

Hey @conda-forge/help-python-c, I think we are ready for the next step here. Thanks!!

[xhochy]

numpy should be pinned differently

[jrenaud90]

numpy should be pinned differently

Thank you!

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

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

For recipes/TidalPy/meta.yaml:

• ℹ️ top-level output has some malformed specs:

• In section run: ipympl >=0.9.6, <0.10.0 Requirement spec fields should always be space-separated to avoid known issues in conda-build. For example, instead of name =version=build, use name version.* build`.

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

[carterbox]

Suggested change

	- ipympl >=0.9.6, <0.10.0
	- ipympl >=0.9.6,<0.10.0

[carterbox]

The reason this package is not building is because your other package cyrk is not pinning numpy correctly.

When you specify a specific pinning for a package, it overides our channel pinnings and floats up to the newest compatible version in the pinning. We pin different numpy versions for each python version channel-wide to improve compatability amongst packages, but since cyrk overrides this pinning, it has been built with numpy 1.26 for all python versions. This makes it incompatible with our channel pinnings which specify numpy 1.22 for python 3.9.

If you want to enforce both your pinnings and our channel pinnings at the same time, you need to specify the package twice. For example:

  - numpy  # empty version spec will pick up channel pinnings
  - numpy >=1.22,<2  # your pinnings also enforced

CC: @ocefpaf because you reviewed and merged the feedstock for cyrk

[ocefpaf]

Should fix it in the other package feedstock.