|
From: Fernando P. <Fer...@co...> - 2004-04-20 17:18:21
|
Andre Wobst wrote: > Absolutely right. It was a bad design from the very beginning. We > included ~/usr/local/lib/python/pyx/lfs only, because we needed it for > CVS and local running (without using distutils and setup.py). When > installing PyX via setup.py we really need to store the path to the > share directory to have it available later on and do not include the > ~/usr/local/lib/python/pyx/lfs anymore. I've patched setup.py > accordingly and introduced a siteconfig.py (which is temporarily > overwritten during install). IFAIK this is the solution to go. (Any > distutils expert around?) We could step further and could define the > "/etc/pyxrc" position along the same lines. The later is an open issue > as well. Thanks for addressing this. I noticed you are discussing the finer points of the solution, and running into the usual (and incredibly annoying) limitations of distutils. Good luck with that, it's driven me crazy in the past many times. distutils is great if you only want to do the trivial setup.py of their examples, but it sucks for more complicated things. In particular, getting information out of it (where it puts things, so your program can later know where to look for them) has always been frustrating to me (and it's undocumented as far as I know; reading the source code seems the only way of finding out). Best, and again many thanks for PyX. You have written a tool I'd been dreaming of for several years, but which I'd never had the time or the energy to write myself :) f |