On Wed, 2007-06-13 at 01:10 +0000, SmileyChris wrote: > http://code.djangoproject.com/ticket/4551 raises the issue that the > docs say that PhoneNumberField is a subclass of CharField when really > it's an IntegerField. > > Now that's an easy fix, but looking at the code a bit deeper it seems > that USPhoneNumberField (the default newforms field) is cleaned to > "XXX-XXX-XXXX" (which isn't going to fit back into an integer field > now, is it). > Shouldn't there be a USPhoneNumberWidget handling the formatting, and > the field be cleaning back to an integer?
What happens if a phone number begins with 0 (as some international numbers are given in the U.S.)? Shouldn't it really be a CharField? It sure as heck isn't an integer. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
