On 25/08/2013 11:25, Aymeric Augustin wrote:
On 18 mai 2013, at 14:07, Erik Romijn <[email protected]> wrote:
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.
Yes. Having both only creates confusion for users of Django.
I agree. I don't see any need at all to keep both around. IPv4 addresses
have already been depleted in two areas and the US is due to follow
shortly. Soon it will be IPv6 or nothing for new ventures unless they
can get hold of their IPv4 addresses from someone else.
--
You received this message because you are subscribed to the Google Groups "Django
developers" 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].
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.
