`include_package_data` doesn't work with `find_namespace_packages`

I’m trying to use namespace package discovery together with package data, and those two seem to conflict?

Snippet of setup.cfg:

[options]
package_dir =
    =src
packages = find_namespace:
include_package_data = True

[options.packages.find]
where = src
include_package_data = True

Stdout of trying that:

python setup.py build_py
running build_py
package init file 'src/sphinxcontrib/__init__.py' not found (or not a regular file)
package init file 'src/sphinxcontrib/elements/theme/__init__.py' not found (or not a regular file)
package init file 'src/sphinxcontrib/elements/theme/static/__init__.py' not found (or not a regular file)

[abravalheri]

Hi @moooeeeep, if you are using the src-layout, currently[^1] you need also to specify in your setup.cfg (in addition to package_dir):

[options.packages.find]
where = src

Please have a look on https://setuptools.pypa.io/en/latest/userguide/declarative_config.html#using-a-src-layout for a more contextualized description.

[^1]: We are experimenting with some improved auto-discovery that might make this easier in the future, but for the time being you need the solution described above.

[moooeeeep]

I stumbled upon a similar issue. Consider the package definition here: https://github.com/moooeeeep/python_package_data

Again, what seems to break the installation of my package’s data files, is the automatic package discovery.

I have this in my setup.cfg which works:

[metadata]
name = foo_pkg
version = 0.0.1

[options]
packages=foo_pkg
package_dir=
    =src
include_package_data=True

Whereas this doesn’t (pkgutil.get_data() returns None instead of the file contents):

[metadata]
name = foo_pkg
version = 0.0.1

[options]
packages=find:
package_dir=
    =src
include_package_data=True