Skip to content

Add lerobot python package #30714

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

traversaro
Copy link
Contributor

Preliminary PR for lerobot. Currently not working, but as I will soon leave for summer vacation, I wanted to share the point I reached.

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.

Copy link
Contributor

github-actions bot commented Aug 4, 2025

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

@traversaro
Copy link
Contributor Author

Missing points:

  • Missing draccus package (easy, it is pure python https://pypi.org/project/draccus/#history )
  • Handle the torchcodec package that is only a dependency on Linux and macOS: probably we can make this a soabi fake package, so that we build different variants for linux/macos and Windows

@conda-forge-admin
Copy link
Contributor

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

Here's what I've got...

For recipes/lerobot/recipe.yaml:

  • ❌ The homepage item is expected in the about section.
  • ❌ The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
  • ❌ The recipe must have a build/number section.
  • ❌ license_file entry is missing, but is required.
  • noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.
  • requirements: run: hf-transfer >= 0.1.4 should not contain a space between relational operator and the version, i.e. hf-transfer >=0.1.4

For recipes/lerobot/recipe.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 the pin python ${{ python_min }}.* for the python entry.
    • For the run section of the recipe, you should usually use the pin python >=${{ python_min }} for the python entry.
    • For the tests[].python.python_version or tests[].requirements.run section of the recipe, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or 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).

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants