Fix collection loader iterator for ext modules - #84758
Conversation
|
The test |
|
Plz, rebase to absorb the F41/F40 fix from #84785. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
There's no need to rebase the PR to pick up the fix. Using |
Is that different from just restarting the failing job? Because I did that before posting the comment and expected that it'd work the same but it didn't. |
Yes, unlike |
68d65a7 to
ab9cfe9
Compare
Fixes the collection loader iter_modules logic to return compiled Python extension modules. This loader is used when attempting to call `pkgutil.iter_modules` on a package that is contained inside the `ansible_collections` path. Before extension modules were skipped which would break imports of 3rd party modules that used compiled extensions if it was installed in a Python environment located inside a collection.
Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>
ab9cfe9 to
b03695d
Compare
|
Backport PRs |
SUMMARY
Fixes the collection loader iter_modules logic to return compiled Python extension modules. This loader is used when attempting to call
pkgutil.iter_moduleson a package that is contained inside theansible_collectionspath. Before extension modules were skipped which would break imports of 3rd party modules that used compiled extensions if it was installed in a Python environment located inside a collection.ISSUE TYPE