But I can only see it attached to issue #34900 related to python 3.13, which will be supported by django 5.1. And I am wondering if it will be packed in the next patch release of 4.2 ?
That would be great because for now we stick to 3.11.8 as a workaround but it’s not ideal. Do I need to create a ticket for it to be added in the next patch release?
Thanks, our pipeline wasn’t working anymore this week dued to the version 3.11.9 with this error. We locked to 3.11.8 and it was solved for now. Thanks!