On Sun, Dec 22, 2013 at 7:02 PM, Arky hitmana...@gmail.com wrote:
Hi,
You can easily fix this by downgrading your django-taggit version. A
solution has already patched in this commit.
(https://github.com/translate/pootle/commit/b9de4520be)
More information is available in the comments here:
On 12/23/2013 10:50 AM, Leandro Regueiro wrote:
As Arky said, this issue can be solved if you install a slightly older
release of django-taggit:
(env) $ pip uninstall django-taggit
(env) $ pip install django-taggit==0.11.1
and at the end: $ pootle setup
yes it's work and i have understand
Hi,
You can easily fix this by downgrading your django-taggit version. A
solution has already patched in this commit.
(https://github.com/translate/pootle/commit/b9de4520be)
More information is available in the comments here:
https://github.com/translate/pootle/pull/158
HTH
--arky
i have tryed to upgrate pootle from 2.5.0 by:
pip install --upgrade Pootle=2.5.1-rc1
It's done but now i recive a traceback to every command, for example:
pootle migrate pootle_app --fake 0001
2013-12-21 22:32:00,685 INFO Loading custom settings from
'/root/.pootle/pootle.conf'...
Traceback
