Opened 18 years ago
Closed 18 years ago
#6212 closed (fixed)
models.NullBooleanField.formfield() returns CharField (instead of newforms.NullBooleanField)
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Tried to get an answer on IRC as to whether there was a reason for this omission or whether it's just a bug.
Attachments (2)
Change History (5)
by , 18 years ago
| Attachment: | NullBooleanField_formfield.diff added |
|---|
comment:1 by , 18 years ago
| Component: | Database wrapper → django.newforms |
|---|---|
| Summary: | models.NullBooleanField.formfield() returns CharField (vs NullBooleanField) → models.NullBooleanField.formfield() returns CharField (instead of newforms.NullBooleanField) |
| Triage Stage: | Unreviewed → Accepted |
by , 18 years ago
comment:2 by , 18 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Pretty straight-forward omission. My patch follows the formatting of the others, anonymous' was a bit hackish
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
patch to add the missing method