FloatField in Django Forms is a integer field, for taking input of floating point numbers from user. The default widget for this input is NumberInput.It normalizes to: A Python float. It validates that the given value is a float. It uses MaxValueValidator and MinValueValidator if max_value and min_value are provided. Leading and trailing whitespace is allowed, as in Python’s float() function.
FloatField has following optional arguments:
- max_length and min_length :- If provided, these arguments ensure that the data is at most or at least the given length.
Syntax
field_name = forms.FloatField(**options)
Django form FloatField Explanation
Illustration of FloatField using an Example. Consider a project named neveropen having an app named Lazyroar.
Refer to the following articles to check how to create a project and an app in Django.
Enter the following code into forms.py file of Lazyroar app.
from django import forms # creating a form class GeeksForm(forms.Form): Lazyroar_field = forms.FloatField( ) |
Add the Lazyroar app to INSTALLED_APPS
# Application definition INSTALLED_APPS = [ 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'Lazyroar', ] |
Now to render this form into a view we need a view and a URL mapped to that URL. Let’s create a view first in views.py of Lazyroar app,
from django.shortcuts import render from .forms import GeeksForm # Create your views here. def home_view(request): context = {} context['form'] = GeeksForm() return render( request, "home.html", context) |
Here we are importing that particular form from forms.py and creating an object of it in the view so that it can be rendered in a template.
Now, to initiate a Django form you need to create home.html where one would be designing the stuff as they like. Let’s create a form in home.html.
<form method="POST"> {% csrf_token %} {{ form.as_p }} <input type = "submit" value = "Submit"> </form> |
Finally, a URL to map to this view in urls.py
from django.urls import path # importing views from views..py from .views import home_view urlpatterns = [ path('', home_view ), ] |
Let’s run the server and check what has actually happened, Run
Python manage.py runserver
Thus, an Lazyroar_field FloatField is created by replacing “_” with ” “. It is a field to input floating point numbers from the user.
How to use FloatField ?
FloatField is used for input of float numbers in the database. One can input date of Marks, percentage, etc. Till now we have discussed how to implement FloatField but how to use it in the view for performing the logical part. To perform some logic we would need to get the value entered into field into a python string instance.
In views.py,
from django.shortcuts import render from .forms import GeeksForm # Create your views here. def home_view(request): context = {} if request.method == "POST": form = GeeksForm(request.POST) if form.is_valid(): temp = form.cleaned_data.get("Lazyroar_field") print(type(temp)) else: form = GeeksForm() context['form'] = form return render(request, "home.html", context) |
Let’s try something other than a number in a FloatField.
So it accepts a valid float number input only otherwise validation errors will be seen. Now let’s try entering a valid floating number into the field.
Float data can be fetched using corresponding request dictionary. If method is GET, data would be available in request.GET and if post, request.POST correspondingly. In above example we have the value in temp which we can use for any purpose. Let’s check what type of temp variable is ?
Core Field Arguments
Core Field arguments are the arguments given to each field for applying some constraint or imparting a particular characteristic to a particular Field. For example, adding an argument required = False to FloatField will enable it to be left blank by the user. Each Field class constructor takes at least these arguments. Some Field classes take additional, field-specific arguments, but the following should always be accepted:
| Field Options | Description |
|---|---|
| required | By default, each Field class assumes the value is required, so to make it not required you need to set required=False |
| label | The label argument lets you specify the “human-friendly” label for this field. This is used when the Field is displayed in a Form. |
| label_suffix | The label_suffix argument lets you override the form’s label_suffix on a per-field basis. |
| widget | The widget argument lets you specify a Widget class to use when rendering this Field. See Widgets for more information. |
| help_text | The help_text argument lets you specify descriptive text for this Field. If you provide help_text, it will be displayed next to the Field when the Field is rendered by one of the convenience Form methods. |
| error_messages | The error_messages argument lets you override the default messages that the field will raise. Pass in a dictionary with keys matching the error messages you want to override. |
| validators | The validators argument lets you provide a list of validation functions for this field. |
| localize | The localize argument enables the localization of form data input, as well as the rendered output. |
| disabled. | The disabled boolean argument, when set to True, disables a form field using the disabled HTML attribute so that it won’t be editable by users. |
<!–
–>
Please Login to comment…