#34466: Django 4.2 overwrites user-specified psycopg cursor_factory -------------------------------------+------------------------------------- Reporter: Anders Kaseorg | Owner: Anders | Kaseorg Type: Bug | Status: assigned Component: Database layer | Version: 4.2 (models, ORM) | Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 1 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Florian Apolloner):
* needs_tests: 0 => 1 * stage: Unreviewed => Accepted Comment: Sounds like a legit request, we didn't limit this functionality on purpose but rather by accident. Assuming we fix this we should also make it more pythonic (and I guess I am at fault for it being like it is now) and not check for `is True` but only truthiness. Either way, a test ensuring that we do not regress here would be good. -- Ticket URL: <https://code.djangoproject.com/ticket/34466#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/01070187584a6349-e7b87210-227f-4738-a62f-40a3289a2cf2-000000%40eu-central-1.amazonses.com.