#10895: Improvements in BRCPFField and BRCNPJField in localflavor.br.forms
-------------------------------------------------+--------------------------
Reporter: luizvital | Owner: nobody
Status: new | Milestone:
Component: django.contrib.localflavor | Version: SVN
Resolution: | Keywords: brcpffield,
brcpnjfield, br, localflavor
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------+--------------------------
Comment (by ramalho):
I support the patch, with two suggestions:
1) simplify the API and take only the return_format keyword arg, but make
it default to None. If that argument is not given, then keep the current
behaviour. No need for the other boolean keyword argument, and we are
still backward compatible.
2) also reject 111.111.111-11 222.222.222-22... and so on, because any CPF
composed of one digit repeated eleven times passes the check, but these
are not real CPFs.
--
Ticket URL: <http://code.djangoproject.com/ticket/10895#comment:2>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
