[Biruktie]

Description

Fixes #360.

Python plugins loaded by file location were not registered in sys.modules, which could cause the same plugin to be loaded as multiple module instances when imported elsewhere.

This change:

• preserves module identity when loading Python plugins by location;
• reuses an already-cached module when the file path matches;
• avoids overwriting an existing importable module when a name collision occurs;
• rolls back module registration when plugin loading fails;
• adds tests covering module identity, cache reuse, name collisions, and error rollback;
• updates the plugin API documentation.

How Has This Been Tested?

• Added tests/test_python_plugin_loader.py covering module identity, cache reuse, module name collisions, and error rollback.
• Ran py -m pytest tests/test_python_plugin_loader.py.
• Result: 5 passed.
• Ran the full test suite with py -m pytest.
• The full suite could not complete because of 3 test-collection errors related to missing/unavailable dependencies and existing test-module import conflicts:
  • channels.slack could not be imported in Autotests/mock_slack/test_slack_unwrap.py.
  • RealTgDriver could not be imported during Autotests/mock_telegram collection.
  • py_landlock was not installed for profile/test_policy.py.

Checklist

• PR contains autogenerated code
• Self-review completed
• Test scenarios above are passed with the version of the code from PR

@MartinEbner

[timur-ashkenov]

Hi @Biruktie,
Thanks for the PR and the effort put into this solution. Your check for conflicting modules that are available but not yet imported is a great addition.
We’ve decided to proceed with the parallel PR #389, which also addresses plugin initialization and registry cleanup. We incorporated your import-path collision check into that implementation and credited you as a co-author using Co-authored-by.
I’ll close this PR now to keep the tracker organized. Thanks again for your contribution, and we welcome your future PRs!