On 28/12/12 04:06, John Ralls wrote:
I don't know that that's really the general case. Regardless, when it *is* the case, how does python find the modules? $PYTHONPATH?
By general case, I mean any arbitrary configuration that the user
happens to choose. The user is responsible for ensuring that python
finds the modules. The distutils documentation suggests using the
"user" installation scheme to make this easier. I would expect that
the modules directory will be in the python path. The data
directory is more likely to be elsewhere.
OK. Unless you know how to do it dynamically, though, it doesn't get rid of conf.py.in. That aside, go for it.
I have made the change now in trunk. PREFIXDIR and SYSCONFDIR have
now been removed, and I have added a LOCALE_DIR.
After the build, LOCALE_DIR will point to the files in the build
directory. After installation, it will point to the location of the
Let me know if you have any problems.
It would be nice to remove const.py.in but I can't see how to at the
moment. The packaging (distutils2) module has better facilities for
managing resources. Unfortunately it is not ready yet.