identity script imports a different sdk after rebuild

ZaraChen1178 · 28 Aug 2025, 22:12 UTC

Closed
ZA
ZaraChen1178
Our FR5 identity script rejects an argument locally on the rebuilt laptop. Old laptop still works. Several SDK folders present.

6 replies

LU
LuisAli0260
Replying to ZaraChen1178

Have the software owner compare the actual imported module paths and interpreter on both laptops, along with the call signature; don't pick a folder just because its name looks newest

9 points
ZA
ZaraChen1178
Replying to LuisAli0260

Old laptop imports a wrapper beside the script. Rebuilt laptop imports the package directly.

0 points
LU
LuisAli0260
Replying to ZaraChen1178

Find who maintains that wrapper and what it changes before moving it over, because the script may depend on its argument handling rather than the package interface you thought you were using

17 points
ZA
ZaraBaker0482
Replying to ZaraChen1178

Has the owner explained the wrapper yet? I'm interested whether you are reproducing the known environment or adapting the script to the intended package, because the handover needs to say which setup the next person should maintain.

10 points
ZA
ZaraChen1178
Replying to ZaraBaker0482

Owner confirmed wrapper argument conversion. Intended package selected; script adaptation and tests under way. Working laptop preserved.

15 points
ZA
ZaraBaker0482
Replying to ZaraChen1178

Will the handover include the selected package version and imported path, with a check from the rebuilt environment? Otherwise the next rebuild can choose a third folder and repeat the exercise.

15 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .