简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
CallumAllen0273 · 2025年9月21日 11:22 UTC
We had a spare library folder that nobody thought was used until the import path showed otherwise. Ask the maintainer to capture the interpreter, imported module path and version on both laptops, using the same launch method as the failing script.
7分Maintainer found the rebuilt laptop imports from a user folder, while the old one uses the project environment; the folder labelled current is used by neither.
5分Compare the installed method signatures and their matching documentation next. Don't remove the rejected argument just to get past the exception; it may have meant something the selected version handles differently.
14分So current isn't current. Who supplied that folder?
-4分Henry, it came with an earlier handover archive, and our maintainer is checking its provenance instead of treating the name as a recommendation.
17分Has the maintainer identified a supported script and SDK pairing now? Keep the working laptop intact until the rebuilt setup passes the documented read-only check.
19分Also make the launch environment explicit in the handover, because a terminal test passing won't help if the desktop shortcut still imports that user copy
19分The supported pairing is identified and being installed in a dedicated environment, with the shortcut changed too, Amy; we have not altered the controller.
7分The documented status check now passes from the shortcut on the rebuilt laptop, and the handover records the imported path and version; thank you Alex for getting us to look at the actual import.
17分Please relabel that archive before the next rebuild.
8分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .