create_update: proxy object displayed instead of model verbose name

[Beuc]

I get this kind of error at ​http://localhost:8000/users/10/

No <django.utils.functional.__proxy__ object at 0x85c2fcc> found for {'username__exact': u'10'}

Apparently this is due to its non-unicode expansion:

        # Note: User.Meta.verbose_name == _('user')
        raise Http404("No %s found for %s"
                      % (model._meta.verbose_name, lookup_kwargs))

It's fixed by using a Unicode string:

u"No %s found for %s"

Patch attached.

[Beuc]

However the change apparently requires all verbose_name / verbose_name_plural to be explicitely declared as u"".

Previously I could use:

# -*- coding: utf-8 -*-
...
  verbose_name="établissement"

Now it's necessary to also mark the string as unicode:

# -*- coding: utf-8 -*-
...
  verbose_name=u"établissement"

otherwise I now get:

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128)

This is inconvenient.

[Russell Keith-Magee]

It's not a bug to require unicode strings when defining unicode text. However, the return value for create_update is clearly problematic. I'm not sure just making the string unicode is the right response; HTTP responses need to be ascii strings.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Tim Graham]

I think this has probably been fixed. If not, please reopen with an explanation of how to reproduce (I am not sure what create_update is).