A test to run on top of the testimage infrastructure should be created, this test should check every python package to see specifically which modules it needs, and will create a manifest file (JSON) automatically according to this information, the newly created file can be used to replace the current file. This will ultimately get rid of all the new bugs we keep having every release of python, when some dependency between modules changes, and will make it easier to create new python packages. This test can/should be run either on every release (of yocto or python) or when adding a new package if one is lazy enough to not check the modules the new package needs to work.
Not sure why this needs to use testimage. If we assume that native python is the same version as target python then we can introspect the native python when that is built.
(In reply to comment #1) > Not sure why this needs to use testimage. If we assume that native python > is the same version as target python then we can introspect the native > python when that is built. Completely agreed, should be possible to do it that way.
Done but moving to 2.5, per Richard's request
Fixed in oe-core 3328211afdef8ffb00dd4dff1143959d5412b075.