Changes between Initial Version and Version 1 of Ticket #10491


Ignore:
Timestamp:
Mar 13, 2009, 11:12:58 PM (15 years ago)
Author:
Malcolm Tredinnick
Comment:

Please report only on bug per ticket. This is two bugs:

  1. Passing a unicode-proxy to HttpResponse classes doesn't convert it to ASCII (it assumes a str or str-proxy objects will be passed in).
  2. Calling create() on a reverse ForeignKey causes problems.

I'm editing the description to describe the problem so that people don't have to work it out from the zip file and I'll open a new ticket for the second (entirely separate) problem. The original description was:

this shows <django.utils.functional.__proxy__ object at 0x0110ED10>, not xxx i expected

this bug also occurs when i'm trying to user.message_set.create(message=_(u'xxx'))

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10491

    • Property Component Internationalization → HTTP handling
    • Property Triage Stage Unreviewed → Accepted

  • Ticket #10491 – Description

    initial v1  
    1 this shows {{{<django.utils.functional.__proxy__ object at 0x0110ED10>}}}, not {{{xxx}}} i expected
    2 
    3 this bug also occurs when i'm trying to {{{user.message_set.create(message=_(u'xxx'))}}}
     1Passing a `ugettext_lazy()` object as the argument to `HttpResponseRedirect.__init__` doesn't work.
Back to Top