From 69ac016543f9f00e84da7520fc0e467952885728 Mon Sep 17 00:00:00 2001 From: Nicolas Rabault Date: Wed, 24 Jun 2026 11:30:06 +0200 Subject: [PATCH] docs(configs): clarify the is_remote_target/is_remote split Add a comment explaining why JobConfig keeps both the staticmethod (tests a raw target string from argv before a config exists) and the property (accessor for an existing config instance). --- src/lerobot/configs/default.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/lerobot/configs/default.py b/src/lerobot/configs/default.py index 6d89587b4..b97a38684 100644 --- a/src/lerobot/configs/default.py +++ b/src/lerobot/configs/default.py @@ -164,6 +164,9 @@ class JobConfig: # Hub. A "lerobot" tag is always added; e.g. --job.tags '["lelab"]' adds more. tags: list[str] = field(default_factory=list) + # Two entry points to the same predicate: the staticmethod tests a raw target string + # straight from argv (before any JobConfig exists, to decide dispatch early), while the + # property is the ergonomic accessor for code that already holds a config instance. @staticmethod def is_remote_target(target: str | None) -> bool: """True when `target` names an HF Jobs flavor rather than a local run."""