Bug 13034 - Migrate python namespace packages from pkgutil to native
Summary: Migrate python namespace packages from pkgutil to native
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 6.2
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-21 18:21 UTC by Christopher Larson
Modified: 2026-10-29 15:06 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Larson 2018-11-21 18:21:13 UTC
This mainly applies to the `oe` python package, but potentially also the other extensible python packages like those in scripts, depending on their particular plugin load method. See https://packaging.python.org/guides/packaging-namespace-packages/#creating-a-namespace-package. pkgutil style have limitations that we need to work around one way or the other, either we do this migration, or the oe_import logic needs to reimport all the packages to be imported to ensure new path additions are picked up.
Comment 1 Randy MacLeod 2021-04-29 15:26:29 UTC
Chris is this still relevant now that we don't support python2?
Comment 2 Christopher Larson 2021-05-06 02:38:23 UTC
This is actually *more* relevant now that we don't support python 2, as the PEP that makes native python packages work was added in python 3.3 :)
Comment 3 Randy MacLeod 2021-05-06 15:28:12 UTC
Hopefully you can work on it Chris! :)