FS#37717 - [python-babel] babel data files are not available
Attached to Project:
Community Packages
Opened by (webmeister) - Sunday, 10 November 2013, 09:58 GMT
Last edited by Balló György (City-busz) - Friday, 08 August 2014, 15:10 GMT
Opened by (webmeister) - Sunday, 10 November 2013, 09:58 GMT
Last edited by Balló György (City-busz) - Friday, 08 August 2014, 15:10 GMT
|
Details
Description:
The CLDR (Common Locale Data Repository) data files are missing from the package, so babel has no locale information and cannot apply translations. Calling "python setup.py import_cldr" (as suggested by the error message below) before "python setup.py install" solves this problem. Steps to reproduce: >>> import babel >>> babel.Locale('en', 'US') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.3/site-packages/babel/core.py", line 150, in __init__ raise UnknownLocaleError(identifier) babel.core.UnknownLocaleError: unknown locale 'en_US' >>> babel.Locale.parse('de_DE') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.3/site-packages/babel/core.py", line 284, in parse language = get_global('language_aliases').get(language, language) File "/usr/lib/python3.3/site-packages/babel/core.py", line 53, in get_global _raise_no_data_error() File "/usr/lib/python3.3/site-packages/babel/core.py", line 25, in _raise_no_data_error raise RuntimeError('The babel data files are not available. ' RuntimeError: The babel data files are not available. This usually happens because you are using a source checkout from Babel and you did not build the data files. Just make sure to run "python setup.py import_cldr" before installing the library. |
This task depends upon
Closed by Balló György (City-busz)
Friday, 08 August 2014, 15:10 GMT
Reason for closing: Fixed
Additional comments about closing: python2-babel 1.3-5
Friday, 08 August 2014, 15:10 GMT
Reason for closing: Fixed
Additional comments about closing: python2-babel 1.3-5
Comment by
Claire Charron (undeterminant) -
Tuesday, 22 April 2014, 12:48 GMT
Comment by
Jan Holthuis (Holzhaus) - Saturday,
24 May 2014, 14:33 GMT
I'm experiencing this exact error.
I can reproduce this error, too. Unfortunately, this makes the
python-babel package unusable for me. Please fix this.