Django

Code

Ticket #4004 (closed: duplicate)

Opened 1 year ago

Last modified 1 year ago

Need a newforms.FloatField field

Reported by: tonnzor <tonn81@gmail.com> Assigned to: anonymous
Milestone: Component: Forms
Version: SVN Keywords:
Cc: Triage Stage: Accepted
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Newforms contains IntegerField? for handling sharp numbers, but do not have FloatField? for handling all other numbers.

If this bug is accepted I write a patch.

Attachments

FloatField.diff (5.8 kB) - added by tonnzor <tonn81@gmail.com> on 04/26/07 12:19:23.
FloatField?
FloatField.2.diff (5.9 kB) - added by tonnzor <tonn81@gmail.com> on 04/27/07 07:26:44.
FloatField? (fixed error message)

Change History

04/14/07 18:53:26 changed by Simon G. <dev@simon.net.nz>

  • needs_better_patch changed.
  • stage changed from Unreviewed to Accepted.
  • needs_tests changed.
  • needs_docs changed.

04/23/07 10:10:06 changed by tonnzor <tonn81@gmail.com>

  • owner changed from adrian to anonymous.
  • status changed from new to assigned.
  • has_patch set to 1.

Patch seems a bit complicated, but it supports max_digits and decimal_places parameters (similar to django.db.models.FloatField)

Error messages might be improved.

The patch contains test suite too.

04/23/07 10:17:31 changed by tonnzor <tonn81@gmail.com>

I have a patch, but see no field to attach it to this ticket :(

04/26/07 12:19:23 changed by tonnzor <tonn81@gmail.com>

  • attachment FloatField.diff added.

FloatField?

04/27/07 07:26:44 changed by tonnzor <tonn81@gmail.com>

  • attachment FloatField.2.diff added.

FloatField? (fixed error message)

05/14/07 03:15:19 changed by mtredinnick

See also #3238 for an alternative patch.

05/20/07 10:43:54 changed by mtredinnick

  • status changed from assigned to closed.
  • resolution set to duplicate.

Closign in favour of #2365.

Add/Change #4004 (Need a newforms.FloatField field)




Change Properties
Action