11695 2017-06-20 23:33:59 +0000 Add task to create python manifest(s) automatically 2018-01-22 14:16:56 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.4 x86 Multiple RESOLVED FIXED LET Medium enhancement 2.5 M2 11510 1 alejandro.hernandez ross.burton jose.perez.carranza meta.mr.watcher meta.watcher ross.burton --- --- Don't know oldest_to_newest 74424 0 alejandro.hernandez 2017-06-20 23:33:59 +0000 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. 74478 1 ross.burton 2017-06-22 15:09:31 +0000 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. 74728 2 alejandro.hernandez 2017-07-04 06:20:41 +0000 (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. 76213 3 alejandro.hernandez 2017-08-28 21:44:46 +0000 Done but moving to 2.5, per Richard's request 79180 4 ross.burton 2018-01-22 14:16:56 +0000 Fixed in oe-core 3328211afdef8ffb00dd4dff1143959d5412b075.