Skip to content

Conversation

@tetov
Copy link
Contributor

@tetov tetov commented Nov 3, 2025

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
Copy link
Contributor

github-actions bot commented Nov 3, 2025

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

@conda-forge-admin
Copy link
Contributor

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/python-neo-lzf/recipe.yaml) and found it was in an excellent condition.

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

For recipes/python-neo-lzf/recipe.yaml:

  • ℹ️ License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

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

@tetov
Copy link
Contributor Author

tetov commented Nov 3, 2025

@conda/help-python-c : This is a bit of a trial balloon. pypcd4 (feedstock) now depends on python-neo-lzf instead of python-lzf (feedstock). We could patch the requirement in pypcd4, or add python-neo-lzf as an alternative name to python-lzf here on conda-forge (I think that's possible?).

Any opinions?

(Using github as source for python-neo-lzf since the sdists are not published, but I added a PR for that FledgeXu/python-neo-lzf#1)

@tetov tetov force-pushed the add_python-neo-lzf branch from 53ccb8b to f863dd1 Compare November 3, 2025 19:55
@conda-forge-admin
Copy link
Contributor

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/python-neo-lzf/recipe.yaml) and found it was in an excellent condition.

@tetov
Copy link
Contributor Author

tetov commented Nov 3, 2025

@conda-forge-admin, please ping help-python-c

@conda-forge-webservices
Copy link

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

I was asked to ping @conda-forge/help-python-c and so here I am doing that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants