DavidBrooks0867 · 17 Oct 2025, 04:05 UTC
Report the imported module path and interpreter from that shortcut, before changing the call to suit whichever documentation happens to be open.
9 pointsIt imports the lesson-folder copy. The working machine imports from its managed environment. I had assumed the setup folder won because that is where I installed things, which is not a great lesson to teach.
13 pointsDon't make the lesson directory a dumping ground for libraries. Keep the environment setup separate and documented. Otherwise every archived exercise can bring its own surprise SDK back into class.
20 pointsDoes the handover include the shortcut target? We inherited one that bypassed the environment instructions completely.
21 pointsFiona, would you keep the old lesson copy somewhere for comparison before removing it?
9 pointsYes, Callum, archive it outside the import locations and label what it came from. I mean stop using it as a dependency, not lose the evidence of what the class ran.
10 pointsMaya, the target was missing from our handover. We have it now, along with both imported paths and the installed versions. The course maintainer is choosing the supported environment; I am leaving the script unchanged until that is settled.
10 pointsCompare the documented call signature for the selected SDK as well; identical script text does not guarantee the two imported libraries accept identical arguments.
9 pointsWho maintains that environment after you hand the laptop over?
13 pointsThis discussion is closed to new replies after six months without activity. Last activity: .