You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
exclude_package_data directive not processed #2269
Hi, IIUC, package data refer to non-Python files. I'm not aware of a way to exclude a module inside a package (there might be though, since my experience is limited), but I think you can work-around this by naming the extension of the files. It seems that they are executable, so if you're on an Unix-like OS, removing .py entirely might be a good idea too.
A more canonical way might be to move all those executable out to a directory that you can exclude (or not include) and use absolute imports within their code.
Hi @antoniosap, the answer provided by @McSinyx explains what is happening and provides a nice workaround... I will close the issue for the time being, since the behaviour that you are facing is expected.
I haven't experimented a lot with that, but I suppose you could also try to use a MANIFEST.in file to control which files get included in the distribution... but that is much more cumbersome that the approach suggested by @McSinyx.
Activity
McSinyx commentedon Jul 21, 2020
Hi, IIUC, package data refer to non-Python files. I'm not aware of a way to exclude a module inside a package (there might be though, since my experience is limited), but I think you can work-around this by naming the extension of the files. It seems that they are executable, so if you're on an Unix-like OS, removing
.pyentirely might be a good idea too.A more canonical way might be to move all those executable out to a directory that you can exclude (or not include) and use absolute imports within their code.
abravalheri commentedon Jan 5, 2022
Hi @antoniosap, the answer provided by @McSinyx explains what is happening and provides a nice workaround... I will close the issue for the time being, since the behaviour that you are facing is expected.
I haven't experimented a lot with that, but I suppose you could also try to use a
MANIFEST.infile to control which files get included in the distribution... but that is much more cumbersome that the approach suggested by @McSinyx.