David Hotham
David Hotham
Also the way you have set up the `packages` key in your pyproject.toml files looks suspect. Poetry itself makes use of namespace packages, you likely want to do the same...
the right fix in the example of this issue is to correct the `packages` key, then everything works fine
read up > you likely want to do the same thing that it and poetry-core do https://github.com/python-poetry/poetry-core/blob/bd1ce358dec403c66e62176b11bfad77a51aacfd/pyproject.toml#L15-L17
that trace is not from the installer and therefore is not evidence of a bug. It only shows poetry using the wheel file to derive dependencies: the configuration setting is...
please provide evidence that the poetry installer is installing binary files when asked not to - nothing you have shown so far suggests this
`poetry install -vvv` and look at the output?
you either didn't type enough `v`s or for some reason filtered out all the logs saying "Skipping wheel as requested in no binary policy for package" there is still no...
Your SBOM tool has nothing to do with poetry. I suppose it is likely looking in the poetry lock file: the inclusion of .whl files there still provides no evidence...
suggest that you add the logs that you would like to see in poetry, use them to verify that poetry is behaving correctly, and then submit a merge request so...
yeah, you should make your description shorter. While poetry is currently stuck in its own poetry-specific section of pyproject.toml, the correspondence between "description" and "summary" is kept in the python...