New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account `recursive-include` seems to be ignored. #886

idlesign opened this Issue Dec 12, 2016 · 4 comments


None yet
3 participants

idlesign commented Dec 12, 2016

Regression since v28.5.0
Reported at idlesign/django-sitetree#222
Related to #764
Manifest example:

sdist creates a package without files mentioned in


This comment has been minimized.


idlesign commented Dec 14, 2016

The reason is that the following doesn't include *, so

recursive-include sitetree/templates .html

should rather be

recursive-include sitetree/templates *.html

I'll fix that in my packages, yet I have a suspicion that I'm not the only one.

@jaraco This one could be closed I think, but kept in mind.


This comment has been minimized.


jaraco commented Dec 14, 2016

This seems to be another manifestation of #849. @timheap, it seems we're now in an awkward situation where we're half-compatible with the old behavior (supporting partial matches for global-exclude but not recursive-include).

It seems everybody's instinct is that the old behavior was undesirable. My temptation is to roll back the changes in #853 and clarify the change in behavior in the changelog for 28.5.0 (and of course the new version).

@timheap, how does that sound to you? Would you be willing to put together the patch?


This comment has been minimized.


timheap commented Dec 14, 2016

@jaraco I agree that the old behaviour was undesirable. PR #890 reverts the changes in #853, and adds a note to the changelog about the change in behaviour.


This comment has been minimized.


jaraco commented Dec 24, 2016

Excellent. Thanks @timheap for the fix, released in Setuptools 32.

@jaraco jaraco closed this Dec 24, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment