Roundup Tracker - Issues

Issue 1219689

classification
i18n: locale .mo not always found (0.8.3)
Type: Severity: normal
Components: Web interface Versions:
process
Status: closed fixed
:
: richard : a1s, richard, schlatterbeck
Priority: normal :

Created on 2005-06-13 13:03 by schlatterbeck, last changed 2005-06-21 10:57 by schlatterbeck.

Messages
msg1973 Author: [hidden] (schlatterbeck) Date: 2005-06-13 13:03
Roundup searches for the system default locale in the
directory _default_localedir of the gettext module.
This variable obviously points to the standard path
depending on where python is installed:

- A python installed in /usr/local will have
'/usr/local/share/locale'
- A python installed in /usr will have '/usr/share/locale'

Therefore roundup installed with --prefix=/usr/local
(as option to setup.py) on a system with a
pre-installed python in /usr/bin will fail to find the
.mo, because it is installed to /usr/local/share/locale.

I'm experiencing this with a Debian sarge with
python2.3 in /usr/bin and a self-installed roundup
0.8.3 in /usr/local. A woody system with a custom
python2.3 in /usr/local and *the same* /usr/local/bin
runs fine.

There probably should be a mechanism to define a search
path for locales. My current work-around is a symbolic
link from the locale subdirectory of the tracker home
to the .mo file in /usr/local/share.
msg1974 Author: [hidden] (a1s) Date: 2005-06-14 07:48
Logged In: YES 
user_id=8719

i wonder how does python find modules installed outside
sys.prefix...

please see if this patch fixes your problem:
http://cvs.sourceforge.net/viewcvs.py/roundup/roundup/roundup/i18n.py?r1=1.14&r2=1.15
msg1975 Author: [hidden] (schlatterbeck) Date: 2005-06-21 10:57
Logged In: YES 
user_id=34818

Yes, thanks, the patch works for me.
History
Date User Action Args
2005-06-13 13:03:56schlatterbeckcreate