Previously, when defining how to build a Python package, you can include folders using a line in Manifest.in:
recursive-include my_package/assets *
However, I would like to poetry and the associated pyproject.toml, instead of Manifest.in.
Can pyproject.toml replace Manifest.in? Alternatively, how can poetry be used with Manifest.in?
Yes, poetry aims to completely obsolete the use of Manifest.in files. The assumption is, that every file that is part of your package should also be part of the distributable. So, as long as you follow a more or less standard project structure, things should Just Work™.
And if your package happens to be structured in a strange way, or you want to package files that for some reason aren't in the source folder, you can use the include and exclude sections for that.