`include_package_data` doesn't work with `find_namespace_packages`
Open
Nobody has claimed this yet.
Waiting User Feedback
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
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)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided setup.cfg configuration and run python setup.py build_py to reproduce the missing __init__.py messages. Trace how find_namespace: and include_package_data are handled during the build. Done means namespace package discovery and package-data inclusion work together without those warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100