The rebuilt laptop rejects an argument before our FR10 read-only script contacts anything. The old laptop runs the same script. Several SDK folders, no record of the working import. How should I identify the actual difference before commissioning instead of copying whichever folder looks familiar?
Record the interpreter and loaded module path from each normal launch, with package identity and the rejected method's signature; Python can import a different copy from the one you inspected in Explorer. Compare that with the supported documentation before changing controller or network settings.
Different loaded versions, despite the script files matching. The old launch imports a copy from a support archive. The rebuilt one uses the maintained package, whose method no longer accepts the optional argument where our script supplies it.
Keep the archive for explanation, but don't make reproducing it the success criterion. Have the maintainer choose the supported environment and update the call from its documentation, then record a normal read that proves which controller actually answered.
And verify how the response is handled after that call succeeds, Aisha; getting past argument validation is only the first repaired boundary, not proof that the script reports the returned identity and failure state correctly.
Has the maintainer completed that comparison now? I'd like the normal shortcut checked too, because the terminal test can use a different interpreter without anyone noticing at handover.
Maintainer selected the supported package and corrected the documented call. Its saved success and failure examples pass our interpreter checks, and the normal shortcut returns the intended controller identity after sign-in and reopening. The archive is outside the launch path. Configuration and the working check are now recorded; controller settings were unchanged.