)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":6914,"name":"Tatiana Ovchinnikova","email":"t.v.ovtchinnikova@gmail.com","username":"tmazur"},"change_message_id":"8b41b8557a3a05642706fb8f7cfd47104c0fc389","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"0b8c1225_2734133b","updated":"2026-09-30 21:17:40.000000000","message":"Django 4.2.30 on Python 3.14 is an unsupported combination. Python 3.14 changed copy.copy() on a super proxy so it returns an actual super object instead of a copy of the underlying instance, and super has no __dict__ to assign into. In the test suite this fires via django.test.client.store_rendered_templates, which copies the context on every template_rendered signal, so essentially any test that renders a template through the test client dies, then the 500 handler dies the same way while rendering the debug traceback, which is why the tracebacks are doubled.\n\nI\u0027d suggest suggest moving the pinning vars down into the django42 job so only it stays on 3.13, and let 52/60 inherit py314:\n\n- job:\n    name: horizon-tox-python3-django42\n    parent: horizon-tox-python3-django\n    vars:\n      django_version: \u0027\u003e\u003d4.2,\u003c4.3\u0027\n      tox_envlist: py313\n      bindep_profile: test py313\n      python_version: \"3.13\"\n\nThis would keep the patch\u0027s intent. As the next step we will have to drop horizon-tox-python3-django42 entirely. Django 4.2 has been EOL since April 2026, and the job is testing a combination nobody should deploy. However that requires raising Django version in requirements.txt and coordinating with openstack/requirements, so it is a separate change.","commit_id":"5646ba3d38da914461b3cd14f927e3296a41ddbb"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"c1b3e7c512536665ac22f88cc463a290ad85fbc3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d2192c3a_9c4d0f78","in_reply_to":"0b8c1225_2734133b","updated":"2026-10-01 01:37:46.000000000","message":"Oh, thanks. I was wondering if something in requirements have been change but now the reason is clear.\nI\u0027ve updated the job definition to pin django42 job to py313 for now.","commit_id":"5646ba3d38da914461b3cd14f927e3296a41ddbb"},{"author":{"_account_id":35133,"name":"Jan Jasek","email":"jjasek@redhat.com","username":"janjasek"},"change_message_id":"a47ed28d44db2eb5542e79614b3ee6c5ea4168ac","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"bd2499ff_5aac9a98","updated":"2026-10-02 10:09:05.000000000","message":"LGTM, thanks!","commit_id":"72591591e041e1f9518d68d9c390994ab535b150"},{"author":{"_account_id":6914,"name":"Tatiana Ovchinnikova","email":"t.v.ovtchinnikova@gmail.com","username":"tmazur"},"change_message_id":"2dd5526d1899325ae8b56241a3a227903de5d789","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"794f7682_b2661c96","updated":"2026-10-01 03:21:21.000000000","message":"recheck, unrelated failure","commit_id":"72591591e041e1f9518d68d9c390994ab535b150"}]}
