#26378: Incorrect behavior in GenericIPAddressField with protocol='both',
unpack_ipv4=False
-------------------------------------+-------------------------------------
Reporter: bshen | Owner:
| AmineYaiche
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
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 bshen):
Is this the actual desired behavior? I don't think we want to have mixed
IPv4 and IPv6 representation be invalid when unpack_ipv4 is False. Mixed
IPv4 and IPv6 is still valid IPv6. In fact, this would probably break
existing code written by others that depends on this functionality where
the first IPv4 octet is not 0.
Furthermore, it appears that root cause of the inconsistency is not
addressed, but rather a whole class of valid IPv6 addresses is now marked
invalid.
--
Ticket URL: <https://code.djangoproject.com/ticket/26378#comment:7>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.0065abf319c25b3f8badd1b0edcdb8d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
