Rossetta and django-debug-toolbar problemes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Activate django-debug-toolbar
2. Set rosetta
3. Go to the rosetta url

Rosseta gives an error concerning ascii to unicode translation. Removing
django-debug-toolbar form the configuration makes rosetta work again.

Original issue reported on code.google.com by antoni.aloy@gmail.com on 5 Mar 2010 at 10:37

[GoogleCodeExporter]

Thank you, which version of Rosetta and debug-toolbar are you experiencing this 
with?

Also, could you please paste a stack trace or the error message you get?

Original comment by mbonetti on 5 Mar 2010 at 10:41

[GoogleCodeExporter]

I am having the same issue. I am running Rosetta 0.5.5 and DJango-debug 0.8.3.  
Here is the stack trace

Original comment by qgriff...@gmail.com on 13 Jun 2010 at 7:42

Attachments:

• stacktrace.rtf

[GoogleCodeExporter]

The problems comes from the fact that django-debug-toolbar tries to display the 
content of request.SESSION where Rosetta stores the Python POFile object, among 
others. 

There is a bug with POFile objects that generate the above error when they are 
rendered as Unicode.

I have a workaround for this, which I'm not very fond of, which basically 
pickles the POFile object before storing it in the session, and unpickles it 
the other way around. I'm not sure I want to check this in, though, as polib is 
about to release a new (hopefully fixed) version, and the problem really lies 
in django-debug-toolbar, not Rosetta.

Any thoughts on this? 

Original comment by mbonetti on 15 Jun 2010 at 3:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here you are: http://github.com/robhudson/django-debug-toolbar/issues

Original comment by mbonetti on 3 Jul 2010 at 11:29

[GoogleCodeExporter]

Thanks, it looks that the proper link to the bug is 
http://github.com/robhudson/django-debug-toolbar/issues/#issue/67 so anyone is 
interested he should vote for it or much better solve it.

Original comment by sorin.sb...@gmail.com on 27 Jul 2010 at 1:09

[GoogleCodeExporter]

I just tested this with the trunk versions of the debug-toolbar and rosetta and 
couldn't reproduce the problem.

Could you guys please also give it a try?

Original comment by mbonetti on 16 Feb 2011 at 3:43

[GoogleCodeExporter]

It seems to be working flawlessly. GREAT WORK mbonetti :D

Original comment by jaco...@gmail.com on 16 Feb 2011 at 6:42

[GoogleCodeExporter]

I still get this stacktrace with both projects at the latest release. I 
reported it over on debug-toolbar's tracker a while ago but I'm not sure where 
the issue lies.

https://github.com/robhudson/django-debug-toolbar/issues/#issue/67

Please let me know if there is any way I can help you guys track down this 
issue, or if you would like help testing a fix.

Original comment by paulosw...@gmail.com on 24 Feb 2011 at 2:18

[GoogleCodeExporter]

Just realized people are testing with the trunk version. With a fresh checkout 
of trunk rosetta I got this:

... snipped ...
  File "/Users/poswald/.virtualenvs/hats/lib/python2.6/site-packages/django/template/defaultfilters.py", line 34, in _dec
    args[0] = force_unicode(args[0])
  File "/Users/poswald/.virtualenvs/hats/lib/python2.6/site-packages/django/utils/encoding.py", line 66, in force_unicode
    s = unicode(s)
  File "/Users/poswald/.virtualenvs/hats/src/django-rosetta/rosetta/polib.py", line 553, in __unicode__
    return ret + _BaseFile.__unicode__(self)
  File "/Users/poswald/.virtualenvs/hats/src/django-rosetta/rosetta/polib.py", line 261, in __unicode__
    ret.append(entry.__unicode__(self.wrapwidth))
  File "/Users/poswald/.virtualenvs/hats/src/django-rosetta/rosetta/polib.py", line 878, in __unicode__
    if self.previous_msgctxt:

TemplateSyntaxError: Caught AttributeError while rendering: 'POEntry' object 
has no attribute 'previous_msgctxt'

Original comment by paulosw...@gmail.com on 24 Feb 2011 at 2:49