On Thu, 18 Oct 2018 at 16:19, Jonathan Haigh <[email protected]> wrote: > The venv package (https://docs.python.org/3/library/venv.html) itself is > missing although its source is available within Python 3.5 > (https://www.python.org/ftp/python/3.5.6/Python-3.5.6.tgz). As mentioned > earlier, it seems the issue is because there is no entry in the manifest from > which the various Python 3 modules are created > (https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-devtools/python/python3/python3-manifest.json). > > The manifest is generated from > https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-devtools/python/python3/create_manifest3.py, > and it does not seem obvious to me how to go about correctly adding a new > module to the manifest, using create_manifest3.py or otherwise.
Ah, right. In that case: $ oe-pkgdata-util find-path */*venv*py python3-tests: /usr/lib/python3.5/test/test_venv.py python3-misc: /usr/lib/python3.5/venv/__main__.py python3-misc: /usr/lib/python3.5/venv/__init__.py The files are in the python3-misc package, which is the fallback for everything which isn't explicitly put into another package. I'd say the best fix for this would be to edit the manifest so the venv module goes into the python3-pyvenv package too. Ross -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
