简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
DavidBrooks0867 · 2025年10月17日 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分It 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分Don'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分Does the handover include the shortcut target? We inherited one that bypassed the environment instructions completely.
21分Fiona, would you keep the old lesson copy somewhere for comparison before removing it?
9分Yes, 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分Maya, 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分Compare the documented call signature for the selected SDK as well; identical script text does not guarantee the two imported libraries accept identical arguments.
9分Who maintains that environment after you hand the laptop over?
13分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .