LinBrown0879 · 21 Apr 2025, 08:15 UTC
Print the loaded module path on both machines, the folder you've been looking at might not be the folder Python is using.
7 pointsIt isn't. Old laptop imports from a folder inside the project. New one finds an installed package.
5 pointsCompare the function signatures there. Which copy accepts the argument your script passes?
8 pointsAre you using the same Python environment when launching it? Our shortcut selected a different environment from the terminal, despite both opening the same script.
21 pointsShortcut and terminal agree on each machine. The project copy accepts the argument; installed package doesn't. Now trying to identify where that project copy came from.
13 pointsAny version file or supplier archive left with it? Don't rename the folder final and call the mystery solved.
13 pointsWe had a working laptop become the only backup. Once you identify this copy, keep its source and setup instructions with the cell files rather than inside one person's machine.
2 pointsFound the original archive in the handover email. It matches the project copy. The newer installed package came from whoever rebuilt the laptop.
24 pointsOur old laptop sat under a bench with a do not update note for ages because nobody could recreate its setup. It worked until the battery failed and then we had a much worse day. Who will try your instructions on a clean machine?
14 pointsAnother technician, not me. I've documented the interpreter, imported path and archive version. Controller compatibility is recorded in the existing read-only test notes.
13 pointsDid the clean setup run the documented check?
15 pointsAnd don't change the script just to please the new package while you're reproducing the old setup, that's another job with its own things to check.
16 pointsClean setup imports the identified copy and gets past the argument check. Waiting for cell access for the documented read-only call. Script stayed unchanged.
11 pointsRead-only check passed on the rebuilt laptop. Response matches what our script expects. Archive and setup notes are in the cell handover folder now, which beats the archaeological collection of SDK directories.
0 pointsGood. Keep the import-path check in the diagnostics so the next rebuild tells you immediately which copy it found.
20 pointsThis discussion is closed to new replies after six months without activity. Last activity: .