Opened 6 years ago

Closed 6 years ago

#11932 closed (invalid)

smart_unicode does not always return a unicode

Reported by: rwillmer Owned by: nobody
Component: Uncategorized Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Django 1.0.2, python 2.6

I'm using BeautifulSoup to parse some XML which I then use as filter into the django database.

If I extract a field from the XML, I get an object of class BeautifulSoup.NavigableString.

If I then call smart_unicode(obj), I still have an object of class BeautifulSoup.NavigableString rather than the unicode I was expecting.

If I then use this as a filter into django, .e.g product = Product.objects.get(obj=obj), I get this error:

  File "/var/lib/python-support/python2.6/django/db/models/", line 93, in get
    return self.get_query_set().get(*args, **kwargs)
  File "/var/lib/python-support/python2.6/django/db/models/", line 304, in get
    num = len(clone)
  File "/var/lib/python-support/python2.6/django/db/models/", line 160, in __len__
    self._result_cache = list(self.iterator())
  File "/var/lib/python-support/python2.6/django/db/models/", line 275, in iterator
    for row in self.query.results_iter():
  File "/var/lib/python-support/python2.6/django/db/models/sql/", line 206, in results_iter
    for rows in self.execute_sql(MULTI):
  File "/var/lib/python-support/python2.6/django/db/models/sql/", line 1734, in execute_sql
    cursor.execute(sql, params)
  File "/var/lib/python-support/python2.6/django/db/backends/postgresql/", line 52, in execute
    return self.cursor.execute(smart_str(sql, self.charset), self.format_params(params))
  File "/var/lib/python-support/python2.6/django/db/backends/postgresql/", line 49, in format_params
    return tuple([smart_str(p, self.charset, True) for p in params])
  File "/var/lib/python-support/python2.6/django/utils/", line 95, in smart_str
    return s.encode(encoding, errors)
TypeError: encode() takes at most 2 arguments (3 given)

Change History (1)

comment:1 Changed 6 years ago by kmtracey

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

This looks like a problem with BeautifulSoup, not Django. BeautifulSoup's NavigableString class inherits from unicode, so isinstance(x, unicode) where x is a NavigableString returns True. Thus Django's unicode conversion functions simply return it, since it appears to be unicode already. The problem shown in the traceback is that this NavigableString class overrides the standard unicode encode() method, which takes 3 parameters ( with one that only takes 2: If it is going to inherit from unicode and override the encode method, it should support all the arguments defined for the base encode.

Note: See TracTickets for help on using tickets.
Back to Top