NVIDIA / NVIDIA/IsaacTeleop

`from isaacteleop.deviceio import FullBodyTracker` fails on the published 1.3.131 wheel; docs give no minimum version

Open Beginner friendly
#891 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
385
Forks
88
Avg merge
3d 23h
Merged PRs (30d)
82

Description

Found during internal QA of the 1.4 release.

The tracker reference documents from isaacteleop.deviceio import FullBodyTracker with no version qualifier, but the wheel currently published on PyPI (isaacteleop 1.3.131) exports that tracker under its older name, FullBodyTrackerPico. Anyone following the published page against a pip-installed build gets an ImportError on that one line, while every other tracker import on the same page succeeds — which makes it look like a broken tracker rather than a version skew.

Repro — in a venv with the PyPI wheel:

$ pip install isaacteleop                     # resolves to 1.3.131
$ python -c "from isaacteleop.deviceio import HeadTracker, HandTracker, ControllerTracker, MessageChannelTracker, Generic3AxisPedalTracker"
$ python -c "from isaacteleop.deviceio import FullBodyTracker"
ImportError: cannot import name 'FullBodyTracker' from 'isaacteleop.deviceio'

The first import line exits cleanly; only FullBodyTracker fails.

Cause

1.3.131 exports FullBodyTrackerPico. The rename to FullBodyTracker is in the 1.4 line, where _DEPRECATED_ALIASES = {"FullBodyTrackerPico": "FullBodyTracker"} keeps the old name working. So the documentation is ahead of the published package rather than wrong: docs/source/device/trackers.rst L200.

Suggested fix

Note the minimum version (1.4) beside FullBodyTracker on the trackers page, and mention FullBodyTrackerPico as the former name so people on 1.3.x can find it. Publishing the 1.4 wheel resolves the immediate ImportError for new users, but the version note is worth having independently — it is the only entry on that page whose availability differs from its neighbours.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Update docs/source/device/trackers.rst around line 200. Review the tracker import entries and the 1.3.131 versus 1.4 naming described in the issue. Done means the FullBodyTracker entry states the minimum version is 1.4 and identifies FullBodyTrackerPico as the former 1.3.x name.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.