Force verbose_name to be a unicode object #31
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some cases, <queryset_instance>.model._meta.fields.verbose_name is a unicode object as expected, like: 'name' or 'Name of User' but other in cases, it is a python object representation, like: <django.utils.functional.__proxy__ object at 0xb2a82bac> It is unclear why this is happening, but it turned up when trying to export just the column headers of an empty queryset. By calling unicode, it is forced to be the desired unicode object.
steventlamb
pushed a commit
that referenced
this pull request
Jan 27, 2014
…y_queryset Force verbose_name to be a unicode object
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases, <queryset_instance>.model._meta.fields.verbose_name is
a unicode object as expected, like:
'name' or 'Name of User'
but other in cases, it is a python object representation, like:
<django.utils.functional.proxy object at 0xb2a82bac>
It is unclear why this is happening, but it turned up when trying to
export just the column headers of an empty queryset. By calling unicode,
it is forced to be the desired unicode object.