#25597: Python 3 compatibility error in PostgreSQL array form fields
-------------------------------------+-------------------------------------
Reporter: BertrandBordage | Owner: Tim
| Graham <timograham@…>
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"69e6045ceb18d859a1586bcd5e64f9b786d87c32" 69e6045c]:
{{{
#!CommitTicketReference repository=""
revision="69e6045ceb18d859a1586bcd5e64f9b786d87c32"
[1.8.x] Fixed #25597 -- Fixed crash with SplitArrayField and IntegerField
on invalid value.
Backport of 1f07da3e29c7c3d47968e1c4531dd9bf902575b7 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25597#comment:4>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.192ea68a334fa5412a37bf9f88ff7a28%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.