On 29. Jul, 2013, at 18:05, Johannes Spielmann wrote: > (Thanks for keeping me in CC. I am indeed not subscribed.) > > On 29.07.2013, at 17:29, Ryan Ollos <[email protected]> wrote: > >> >> On Jul 29, 2013 9:36 AM, "Gary Martin" <[email protected]> wrote: >>> >>> (CCing Johannes as I have a suspicion that he is not subscribed to the dev >>> list.) >>> >>> >>> On 29/07/13 13:45, Johannes Spielmann wrote: >>>> >>>> Hi, >>>> >>>> I've just tried to install BloodHound in the 'de' locale and it wouldn't >>>> work with this error trace: >>>> Traceback (most recent call last): >>>> File "bloodhound_setup.py", line 485, in <module> >>>> bsetup.setup() >>>> File "bloodhound_setup.py", line 195, in setup >>>> translation.activate(locale) >>>> File >>>> "/Users/spielmann/prog/bloodhound/bloodhound/trac/trac/util/translation.py", >>>> line 326, in activate >>>> translations.activate(locale, env_path) >>>> File >>>> "/Users/spielmann/prog/bloodhound/bloodhound/trac/trac/util/translation.py", >>>> line 153, in activate >>>> t.add(Translations.load(locale_dir, locale or 'en_US', >>>> AttributeError: 'NullTranslations' object has no attribute 'add' >>>> >>>> Changing the rather unusual test in line 149 of >>>> /trac/trac/util/translation.py to a regular isinstance test seems to fix >>>> the issue. A patch is attached. >>>> >>>> Cheers, >>>> Johannes >>>> >>> >>> Thanks for that Johannes. Though this patch is effectively for trac, I >>> suspect that a lot of our users will experience problems so I am very happy >>> for you to have brought it up for us. >>> >>> In fact, this problem also seems to have turned up on our demo servers >>> which, up until recently, were building correctly. Seems like we probably >>> need to look into why this should suddenly be the case. >>> >>> Cheers, >>> Gary >> >> Could be related to the release of babel 1.1, 1.2 and 1.3 over the weekend. >> >> http://trac.edgewall.org/ticket/11258 >> >> Which babel version are you Running? >> > > FYI: I followed the regular install instructions and it pulled Babel==1.3 >
I can confirm the issue is related to Babel. The setup even fails with en_US.UTF-8 encoding, and installing Babel==0.9.6 resolves the issue. -- matevz
