Phillip J. Eby
You might want to just include all your data and/or header files inside your package directory; this is the one directory you can always find at runtime, no matter how your package gets installed.
I'm not sure I understand. Are you suggesting to ignore/override what the user specifies with --install-headers or similar options?
I'm suggesting that if your package needs to have a reliable location for the data, then it should include it with the package. This is orthogonal to whether you *also* install the headers in a user-specified location. I'm just saying that if you have the data in your package, you no longer have to care where the user may have *also* put it.
OK, so you're suggesting to install two copies of the same files: one in a fixed location (within site-packages) so that it's always accessible, and a copy for the user wherever he wants. This might work for my case, but how do I implement it? Do I need to override most of the install_* cmd to implement this logic, or there is some trick I can exploit? Thanks! Giovanni Bajo