➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: gettext should honor $LOCPATH environment variable
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.1, Python 3.2, Python 2.7
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: barry, dsegan, eric.araujo, lemburg, loewis, rpetrov
Priority: normal Keywords: easy

Created on 2010-04-15 14:28 by barry, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg103220 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2010-04-15 14:28 
LOCPATH is an environment variable recognized by locale(1)

http://man.he.net/?topic=locale&section=all

gettext.find() should probably consult $LOCPATH and use that for localedir if the argument is not given.
msg103257 - (view) Author: Roumen Petrov (rpetrov) * Date: 2010-04-15 21:05 
LOCPATH is not used by GNU gettext.
/usr/share/locale/XX/... - message translation files (GNU gettext)
/usr/lib/locale/xx_XX*/ - locale (GNU libc)
msg120532 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-11-05 20:46 
Should this be closed as invalid?
msg120533 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2010-11-05 20:48 
I'm not an expert on this, but I think it's still valid.  Maybe Martin has an opinion on it?
msg143314 - (view) Author: Danilo Segan (dsegan) Date: 2011-09-01 09:11 
I believe it's invalid. GNU gettext itself doesn't honor the LOCPATH variable, LOCPATH is basically used by GNU libc for pointing to locale data. Even though this also includes LC_MESSAGES, gettext has never used it afaik.

If it's not invalid (iow, gettext should use it), it'd first need to be fixed upstream in GNU gettext.

FWIW, I've grepped for any occurrence of LOCPATH in upstream gettext git tree and it returned zero results.
History
Date User Action Args
2022-04-11 14:56:59adminsetgithub: 52656
2011-09-01 11:38:08barrysetstatus: open -> closed
resolution: not a bug
2011-09-01 09:11:11dsegansetnosy: + dsegan
messages: + msg143314
2010-11-05 20:48:42barrysetmessages: + msg120533
2010-11-05 20:46:34eric.araujosetnosy: + loewis, eric.araujo, lemburg
messages: + msg120532
2010-10-25 19:34:57barrysetassignee: barry ->
2010-04-15 21:05:46rpetrovsetnosy: + rpetrov
messages: + msg103257
2010-04-15 14:28:44barrysetversions: + Python 3.1, Python 2.7
2010-04-15 14:28:35barrysetversions: - Python 3.1, Python 2.7
2010-04-15 14:28:12barrycreate