Django4: TemplateTagTests.test_site_branding_tag test failure in Debian unstable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Low
|
Akihiro Motoki |
Bug Description
Hi,
Building Horizon (yoga) in Debian Unstable resulted in failure with TemplateTagTest
___________________ TemplateTagTest
[gw9] linux -- Python 3.9.13 /usr/bin/python3.9
self = <horizon.
def test_site_
"""Test if site_branding tag renders the correct setting."""
> rendered_str = self.render_
horizon/
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
horizon/
return self.render_
horizon/
return template.
/usr/lib/
return self._render(
/usr/lib/
return self.nodelist.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = [<django.
context = [{'True': True, 'False': False, 'None': None}, {}]
def render(self, context):
> return SafeString(
E TypeError: sequence item 2: expected str instance, __proxy__ found
summary: |
- TemplateTagTests.test_site_branding_tag test failure in Debian unstable - with Horizon / Yoga + Django4: TemplateTagTests.test_site_branding_tag test failure in Debian + unstable with Horizon / Yoga |
Changed in horizon: | |
assignee: | nobody → Akihiro Motoki (amotoki) |
importance: | Undecided → Low |
status: | New → Confirmed |
Perhaps it is specific to Django 4, but no information is not provided in the description.
Could you add more detail info on the environment in Debian unstable so that the upstream can track the issue?