id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 20439 Deprecate IPAddressField in favour of GenericIPAddressField Sasha Romijn Aymeric Augustin "Since Django 1.4, we've added `GenericIPAddressField`, next to `IPAddressField`. The new GenericIPAddressField supports IPv4 as well as IPv6 addresses, and does normalisation of IPv6 addresses. It can also be configured to only accept IPv4 or IPv6 addresses. As far as I know, IPAddressField has no current features that are not also available in a GenericIPAddressField. Therefore, I suggest that we, some time from now, deprecate IPAddressField, in favour of GenericIPAddressField. For users, it is database-dependent whether IPAddressFields can just be replaced with GenericIPAddressFields: on PostgreSQL and SQLite, no changes are needed; schema changes are needed on MySQL and Oracle. Examples are listed in the 1.6 release notes [https://docs.djangoproject.com/en/dev/releases/1.6/#storage-of-ip-addresses-in-the-comments-app], as we just made the same change for comments." Cleanup/optimization closed Database layer (models, ORM) dev Normal fixed dceu13 eromijn@… mike@… Ready for checkin 1 0 0 0 0 0