On Tue, Dec 14, 2010 at 7:39 PM, P.J. Eby firstname.lastname@example.org wrote:
At 07:30 PM 12/14/2010 +0100, Arve Knudsen wrote:
On Tue, Dec 14, 2010 at 7:22 PM, P.J. Eby <mailto:email@example.com
firstname.lastname@example.org> wrote: At 06:30 PM 12/14/2010 +0100, Arve Knudsen wrote: Argh :( Can you describe some other way of customizing the install command that works better with setuptools?
That depends on what you're trying to do; but probably it will involve subclassing the install command rather than simply invoking it.
What are you trying to customize, anyway? There really aren't many user-serviceable parts inside; you'd probably be better off customizing subcommands (like install_lib or some of the build_* commands).
I don't have the project in front of me right now, but what I needed to do was to install something non-Python. That is, if the package gets installed under <prefix>/lib, the extra data gets installed under <prefix>/data. The data is part of the project, but not part of the Python package(s).
That's not going to work except in the old-style installation mode. With a setuptools or distribute project, your only places to store data are inside the package or in the metadata (e.g. a subdirectory inside .egg-info).
I'm aware of that issue, but it doesn't matter in this case, since the data are really orthogonal to the Python distribution (and the project is proprietary).