include must be specific to poetry, I didn’t realize that. I’ll have to look up what the setup tools equivalent is.

include must be specific to poetry, I didn’t realize that. I’ll have to look up what the setup tools equivalent is.

Yes, I was looking for an equivalent and I thought it was build-backend but it didn't seams to fix the issue.
I found this but haven't had time to check it yet:

[tool.poetry]
# ...
packages = [
    { include = "my_package" },
    { include = "extra_package/**/*.py" },
]

It looks like this will still be poetry specific with [tool.poetry]. But if you are wanting to switch from pipenv to poetry you would get no arguments from me 😄

I did a little searching and didn’t find a way to include it in the pyproject.toml using setup tools. This surprises me so I could just not be finding it. What we may need to do is include the py.typed in a MANIFEST.in file.