Log file Viewer

[15:46:09] <ngaio> If I run sudo python setup.py install and I put a relative path in data_files in the setup() section of setup.py, the files end up in the egg. If I put an absolute path, they end up in the right place as expected. On the other hand I install the tar created by sdist, the data files end up in the correct location. Is this normal? Or am I doing something wrong?

[15:46:44] <ngaio> On the other hand if I install *

[15:48:12] <ngaio> what I'm trying to say (perhaps very badly) is that using pip to install produces a different result with the data files than if I run python setup.py install

[15:48:23] <ngaio> with pip it works

[15:49:19] <ngaio> with python setup.py install the data_files are all installed in the egg, which is not good when they things like Linux man pages

[17:09:14] <ngaio> ok so from more reading now I see I'm running into this complex bug/feature with data_files and conflicting ideas about whether it makes sense to install files in a place like /usr/share/icons, or not

[17:41:52] <ngaio> it's an extremely confusing situation

[17:52:31] <tdsmith> a lot of things in that scenario have fallen out of favor

[17:53:09] <tdsmith> installing packages with easy_install (setup.py install) and getting eggs aren't trendy and neither is installing packages as root, so data_files putting stuff in system locations is also out of fashion

[18:37:30] <ngaio> tdsmith, so it seems Linux users should not be able to install a python desktop app and expect there to be menu launchers, man page, etc?

[20:08:16] <tdsmith> not with pip, anyway

[20:08:30] <tdsmith> system package managers can handle that better