Sorry for the terrible description above. This is still a real problem. But I found a way to still get the functionality of pbr to work while still using setuptools properly.
Put an [options] section in setup.cfg since setuptools supports setup.cfg style config now. Specify
[options]
package_dir = src/
packages = boardgame_framework
SetupTools will accept that info and still play well with pbr. Stop using [files] section of pbr.
You still get all the autogeneration goodness of pbr with authors, changelog, version number, release notes, etc....and you get proper sdist and installs!
I plan to keep looking at the behavior in pbr to see if I can fix it but I'm putting this info here in case a "real" pbr developer can connect the dots on what info is not being forwarded around properly.
Sorry for the terrible description above. This is still a real problem. But I found a way to still get the functionality of pbr to work while still using setuptools properly.
Put the `package_ dir={'' :'src/' } in the setup.py (this is needed as per a warning on https:/ /setuptools. readthedocs. io/en/latest/ setuptools. html#configurin g-setup- using-setup- cfg-files under "Using find_packages".
Put an [options] section in setup.cfg since setuptools supports setup.cfg style config now. Specify
[options]
package_dir = src/
packages = boardgame_framework
SetupTools will accept that info and still play well with pbr. Stop using [files] section of pbr.
You still get all the autogeneration goodness of pbr with authors, changelog, version number, release notes, etc....and you get proper sdist and installs!
I plan to keep looking at the behavior in pbr to see if I can fix it but I'm putting this info here in case a "real" pbr developer can connect the dots on what info is not being forwarded around properly.