A widget is Django's representation of an HTML input element. The widget\nhandles the rendering of the HTML, and the extraction of data from a GET/POST\ndictionary that corresponds to the widget.
\nThe HTML generated by the built-in widgets uses HTML5 syntax, targeting\n<!DOCTYPE html>. For example, it uses boolean attributes such as checked\nrather than the XHTML style of checked='checked'.
Whenever you specify a field on a form, Django will use a default widget\nthat is appropriate to the type of data that is to be displayed. To find\nwhich widget is used on which field, see the documentation about\nKelaS-kelas Field siap-pakai.
\nHowever, if you want to use a different widget for a field, you can\nuse the widget argument on the field definition. For example:
from django import forms\n\n\nclass CommentForm(forms.Form):\n name = forms.CharField()\n url = forms.URLField()\n comment = forms.CharField(widget=forms.Textarea)\nIni akan menentukan formulir dengan komentar yang menggunakan widget Textarea terbesar, daripada widget TextInput awal.
Many widgets have optional extra arguments; they can be set when defining the\nwidget on the field. In the following example, the\nyears attribute is set for a\nSelectDateWidget:
from django import forms\n\nBIRTH_YEAR_CHOICES = ["1980", "1981", "1982"]\nFAVORITE_COLORS_CHOICES = {\n "blue": "Blue",\n "green": "Green",\n "black": "Black",\n}\n\n\nclass SimpleForm(forms.Form):\n birth_year = forms.DateField(\n widget=forms.SelectDateWidget(years=BIRTH_YEAR_CHOICES)\n )\n favorite_colors = forms.MultipleChoiceField(\n required=False,\n widget=forms.CheckboxSelectMultiple,\n choices=FAVORITE_COLORS_CHOICES,\n )\nLihat Widget pasang tetap untuk informasi lebih tentang widget-widget mana tersedia dan argumen mana mereka terima.
\nSelectLink to this heading#Widgets inheriting from the Select widget deal with choices. They\npresent the user with a list of options to choose from. The different widgets\npresent this choice differently; the Select widget itself uses a\n<select> HTML list representation, while RadioSelect uses radio\nbuttons.
Select widgets are used by default on ChoiceField fields. The\nchoices displayed on the widget are inherited from the ChoiceField and\nchanging ChoiceField.choices will update Select.choices. For\nexample:
>>> from django import forms\n>>> CHOICES = {"1": "First", "2": "Second"}\n>>> choice_field = forms.ChoiceField(widget=forms.RadioSelect, choices=CHOICES)\n>>> choice_field.choices\n[('1', 'First'), ('2', 'Second')]\n>>> choice_field.widget.choices\n[('1', 'First'), ('2', 'Second')]\n>>> choice_field.widget.choices = []\n>>> choice_field.choices = [("1", "First and only")]\n>>> choice_field.widget.choices\n[('1', 'First and only')]\nWidgets which offer a choices attribute can however be used\nwith fields which are not based on choice -- such as a CharField --\nbut it is recommended to use a ChoiceField-based field when the\nchoices are inherent to the model and not just the representational widget.
When Django renders a widget as HTML, it only renders very minimal markup -\nDjango doesn't add class names, or any other widget-specific attributes. This\nmeans, for example, that all TextInput widgets will appear the same\non your web pages.
Ada dua cara menyesuaikan widget: per widget instance dan per widget class.
\nIf you want to make one widget instance look different from another, you will\nneed to specify additional attributes at the time when the widget object is\ninstantiated and assigned to a form field (and perhaps add some rules to your\nCSS files).
\nFor example, take the following form:
\nfrom django import forms\n\n\nclass CommentForm(forms.Form):\n name = forms.CharField()\n url = forms.URLField()\n comment = forms.CharField()\nThis form will include TextInput widgets for the name and comment\nfields, and a URLInput widget for the url field. Each has default\nrendering - no CSS class, no extra attributes:
>>> f = CommentForm(auto_id=False)\n>>> print(f)\n<div>Name:<input type="text" name="name" required></div>\n<div>Url:<input type="url" name="url" required></div>\n<div>Comment:<input type="text" name="comment" required></div>\nOn a real web page, you probably want to customize this. You might want a\nlarger input element for the comment, and you might want the 'name' widget to\nhave some special CSS class. It is also possible to specify the 'type'\nattribute to use a different HTML5 input type. To do this, you use the\nWidget.attrs argument when creating the widget:
class CommentForm(forms.Form):\n name = forms.CharField(widget=forms.TextInput(attrs={"class": "special"}))\n url = forms.URLField()\n comment = forms.CharField(widget=forms.TextInput(attrs={"size": "40"}))\nAnda dapat juga merubah widget dalam pengertian formulir:
\nclass CommentForm(forms.Form):\n name = forms.CharField()\n url = forms.URLField()\n comment = forms.CharField()\n\n name.widget.attrs.update({"class": "special"})\n comment.widget.attrs.update(size="40")\nAtau jika bidang tidak dinyatakan langsung pada formulir (seperti bidang formulir model), anda dapat menggunakan atribut Form.fields:
class CommentForm(forms.ModelForm):\n def __init__(self, *args, **kwargs):\n super().__init__(*args, **kwargs)\n self.fields["name"].widget.attrs.update({"class": "special"})\n self.fields["comment"].widget.attrs.update(size="40")\nDjango kemudian akan menyertakan atribut tambahan dalam keluaran dibangun:
\n>>> f = CommentForm(auto_id=False)\n>>> print(f)\n<div>Name:<input type="text" name="name" class="special" required></div>\n<div>Url:<input type="url" name="url" required></div>\n<div>Comment:<input type="text" name="comment" size="40" required></div>\nAnda dapat juga mensetel id HTML menggunakan attrs. Lihat BoundField.id_for_label sebagai contoh.
Dengan widget, itu memungkinkan menambahkan assets (css dan javascript) dan lebih mendalam menyesuaikan penampilan dan perilaku mereka.
In a nutshell, you will need to subclass the widget and either\ndefine a "Media" inner class or\ncreate a "media" property.
\nThese methods involve somewhat advanced Python programming and are described in\ndetail in the Form Assets topic guide.
\nBase widget classes Widget and MultiWidget are subclassed by\nall the built-in widgets and may serve as a\nfoundation for custom widgets.
WidgetLink to this heading#This abstract class cannot be rendered, but provides the basic attribute\nattrs. You may also implement or override the\nrender() method on custom widgets.
Sebuah dictionary mengandung atribut HTML untuk disetel pada widget dibangun.
\n>>> from django import forms\n>>> name = forms.TextInput(attrs={"size": 10, "title": "Your name"})\n>>> name.render("name", "A name")\n'<input title="Your name" type="text" name="name" value="A name" size="10">'\nIf you assign a value of True or False to an attribute,\nit will be rendered as an HTML5 boolean attribute:
>>> name = forms.TextInput(attrs={"required": True})\n>>> name.render("name", "A name")\n'<input name="name" type="text" value="A name" required>'\n>>>\n>>> name = forms.TextInput(attrs={"required": False})\n>>> name.render("name", "A name")\n'<input name="name" type="text" value="A name">'\nSebuah atribut yang awalan menjadi True. Jika disetel menjadi False, mikrodetik bagian dari nilai-nilai datetime dan time akan disetel menjadi 0.
Cleans and returns a value for use in the widget template. value\nisn't guaranteed to be valid input, therefore subclass implementations\nshould program defensively.
Returns a dictionary of values to use when rendering the widget\ntemplate. By default, the dictionary contains a single key,\n'widget', which is a dictionary representation of the widget\ncontaining the following keys:
'name': Nama dari bidang dari argumen name.
'is_hidden': Sebuah boolean menunjukkan apakah atau tidak widget ini tersembunyi.
'required': Sebuah boolean menunjukkan apakah atau tidak bidang untuk widget ini diwajibkan.
'value': Nilai seperti dikembalikan oleh format_value().
'attrs': Atribut-atribut HTML untuk disetel pada widget dibangun. Perpaduan dari atribut attrs dan argumen attrs.
'template_name': Nilai dari self.template_name.
Subkelas-subkelas Widget dapat menyediakan penyesuaian nilai konteks dengan menimpa metode ini.
Returns the HTML ID attribute of this widget for use by a <label>,\ngiven the ID of the field. Returns an empty string if an ID isn't\navailable.
This hook is necessary because some widgets have multiple HTML\nelements and, thus, multiple IDs. In that case, this method should\nreturn an ID value that corresponds to the first ID in the widget's\ntags.
\nRenders a widget to HTML using the given renderer. If renderer is\nNone, the renderer from the FORM_RENDERER setting is\nused.
Given a dictionary of data and this widget's name, returns the value\nof this widget. files may contain data coming from\nrequest.FILES. Returns None\nif a value wasn't provided. Note also that value_from_datadict may\nbe called more than once during handling of form data, so if you\ncustomize it and add expensive processing, you should implement some\ncaching mechanism yourself.
Given data and files dictionaries and this widget's name,\nreturns whether or not there's data or files for the widget.
Hasil metode mempengaruhi apakah atau tidak sebuah bidang di sebuah model formulir falls back to its default.
\nSpecial cases are CheckboxInput,\nCheckboxSelectMultiple, and\nSelectMultiple, which always return\nFalse because an unchecked checkbox and unselected\n<select multiple> don't appear in the data of an HTML form\nsubmission, so it's unknown whether or not the user submitted a value.
An attribute to identify if the widget should be grouped in a\n<fieldset> with a <legend> when rendered. Defaults to False\nbut is True when the widget contains multiple <input> tags such as\nCheckboxSelectMultiple,\nRadioSelect,\nMultiWidget,\nSplitDateTimeWidget, and\nSelectDateWidget.
Given a form field's initial value, returns whether or not the\nwidget can be rendered with the required HTML attribute. Forms use\nthis method along with Field.required and Form.use_required_attribute to determine whether or not\nto display the required attribute for each field.
By default, returns False for hidden widgets and True\notherwise. Special cases are FileInput and\nClearableFileInput, which return False when\ninitial is set, and CheckboxSelectMultiple,\nwhich always returns False because browser validation would require\nall checkboxes to be checked instead of at least one.
Override this method in custom widgets that aren't compatible with\nbrowser validation. For example, a WSYSIWG text editor widget backed by\na hidden textarea element may want to always return False to\navoid browser validation on the hidden field.
MultiWidgetLink to this heading#A widget that is composed of multiple widgets.\nMultiWidget works hand in hand with the\nMultiValueField.
MultiWidget mempunyai satu argumen diwajibkan:
An iterable containing the widgets needed. For example:
\n>>> from django.forms import MultiWidget, TextInput\n>>> widget = MultiWidget(widgets=[TextInput, TextInput])\n>>> widget.render("name", ["john", "paul"])\n'<input type="text" name="name_0" value="john"><input type="text" name="name_1" value="paul">'\nYou may provide a dictionary in order to specify custom suffixes for\nthe name attribute on each subwidget. In this case, for each\n(key, widget) pair, the key will be appended to the name of the\nwidget in order to generate the attribute value. You may provide the\nempty string ('') for a single key, in order to suppress the suffix\nfor one widget. For example:
>>> widget = MultiWidget(widgets={"": TextInput, "last": TextInput})\n>>> widget.render("name", ["john", "paul"])\n'<input type="text" name="name" value="john"><input type="text" name="name_last" value="paul">'\nDan satu cara diwajibkan:
\nThis method takes a single "compressed" value from the field and\nreturns a list of "decompressed" values. The input value can be\nassumed valid, but not necessarily non-empty.
\nThis method must be implemented by the subclass, and since the\nvalue may be empty, the implementation must be defensive.
\nThe rationale behind "decompression" is that it is necessary to "split"\nthe combined value of the form field into the values for each widget.
\nAn example of this is how SplitDateTimeWidget turns a\ndatetime value into a list with date and time split\ninto two separate values:
from django.forms import MultiWidget\n\n\nclass SplitDateTimeWidget(MultiWidget):\n # ...\n\n def decompress(self, value):\n if value:\n return [value.date(), value.time()]\n return [None, None]\nItu menyediakan beberapa konteks penyesuaian:
\nIn addition to the 'widget' key described in\nWidget.get_context(), MultiWidget adds a\nwidget['subwidgets'] key.
Ini dapat dilingkarkan dalam cetakan widget:
\n{% for subwidget in widget.subwidgets %}\n {% include subwidget.template_name with widget=subwidget %}\n{% endfor %}\nHere's an example widget which subclasses MultiWidget to display\na date with the day, month, and year in different select boxes. This widget\nis intended to be used with a DateField rather than\na MultiValueField, thus we have implemented\nvalue_from_datadict():
from datetime import date\nfrom django import forms\n\n\nclass DateSelectorWidget(forms.MultiWidget):\n def __init__(self, attrs=None):\n days = {day: day for day in range(1, 32)}\n months = {month: month for month in range(1, 13)}\n years = {year: year for year in [2018, 2019, 2020]}\n widgets = [\n forms.Select(attrs=attrs, choices=days),\n forms.Select(attrs=attrs, choices=months),\n forms.Select(attrs=attrs, choices=years),\n ]\n super().__init__(widgets, attrs)\n\n def decompress(self, value):\n if isinstance(value, date):\n return [value.day, value.month, value.year]\n elif isinstance(value, str):\n year, month, day = value.split("-")\n return [day, month, year]\n return [None, None, None]\n\n def value_from_datadict(self, data, files, name):\n day, month, year = super().value_from_datadict(data, files, name)\n # DateField expects a single string that it can parse into a date.\n return "{}-{}-{}".format(year, month, day)\nThe constructor creates several Select widgets in a list. The\nsuper() method uses this list to set up the widget.
The required method decompress() breaks up a\ndatetime.date value into the day, month, and year values corresponding\nto each widget. If an invalid date was selected, such as the non-existent\n30th February, the DateField passes this method a\nstring instead, so that needs parsing. The final return handles when\nvalue is None, meaning we don't have any defaults for our\nsubwidgets.
The default implementation of value_from_datadict() returns a\nlist of values corresponding to each Widget. This is appropriate when\nusing a MultiWidget with a MultiValueField. But\nsince we want to use this widget with a DateField,\nwhich takes a single value, we have overridden this method. The\nimplementation here combines the data from the subwidgets into a string in\nthe format that DateField expects.
Django provides a representation of all the basic HTML widgets, plus some\ncommonly used groups of widgets in the django.forms.widgets module,\nincluding the input of text, various checkboxes\nand selectors, uploading files,\nand handling of multi-valued input.
Widget ini membuat penggunaan dari unsur-unsur HTML input` dan ``textarea.
TextInputLink to this heading#input_type: 'text'
template_name: 'django/forms/widgets/text.html'
Membangun sebagai: <input type="text" ...>
NumberInputLink to this heading#input_type: 'number'
template_name: 'django/forms/widgets/number.html'
Membangun sebagai: <input type="number" ...>
Beware that not all browsers support entering localized numbers in\nnumber input types. Django itself avoids using them for fields having\ntheir localize property set to True.
EmailInputLink to this heading#input_type: 'email'
template_name: 'django/forms/widgets/email.html'
Membangun sebagai: <input type="email" ...>
URLInputLink to this heading#input_type: 'url'
template_name: 'django/forms/widgets/url.html'
Membangun sebagai: <input type="url" ...>
ColorInputLink to this heading#input_type: 'color'
template_name:'django/forms/widgets/color.html'
Renders as: <input type="color" ...>
SearchInputLink to this heading#input_type: 'search'
template_name: 'django/forms/widgets/search.html'
Renders as: <input type="search" ...>
TelInputLink to this heading#input_type: 'tel'
template_name: 'django/forms/widgets/tel.html'
Renders as: <input type="tel" ...>
Browsers perform no client-side validation by default because telephone\nnumber formats vary so much around the world. You can add some by setting\npattern, minlength, or maxlength in the Widget.attrs\nargument.
Additionally, you can add server-side validation to your form field with a\nvalidator like RegexValidator or via\nthird-party packages, such as django-phonenumber-field.
PasswordInputLink to this heading#input_type: 'password'
template_name: 'django/forms/widgets/password.html'
Membangun sebagai: <input type="password" ...>
Mengambil satu argumen pilihan:
\nDetermines whether the widget will have a value filled in when the\nform is re-displayed after a validation error (default is False).
DateInputLink to this heading#input_type: 'text'
template_name: 'django/forms/widgets/date.html'
Membangun sebagai: <input type="text" ...>
Mengambil argumen sama seperti TextInput, dengan satu atau lebih argumen pilihan:
Bentuk dimana nilaiinisial bidang ini akan ditampilkan.
\nIf no format argument is provided, the default format is the first\nformat found in DATE_INPUT_FORMATS and respects\nBentuk lokalisasi. %U, %W, and %j formats are not\nsupported by this widget.
DateTimeInputLink to this heading#input_type: 'text'
template_name: 'django/forms/widgets/datetime.html'
Membangun sebagai: <input type="text" ...>
Mengambil argumen sama seperti TextInput, dengan satu atau lebih argumen pilihan:
Bentuk dimana nilaiinisial bidang ini akan ditampilkan.
\nIf no format argument is provided, the default format is the first\nformat found in DATETIME_INPUT_FORMATS and respects\nBentuk lokalisasi. %U, %W, and %j formats are not\nsupported by this widget.
By default, the microseconds part of the time value is always set to 0.\nIf microseconds are required, use a subclass with the\nsupports_microseconds attribute set to True.
TimeInputLink to this heading#input_type: 'text'
template_name: 'django/forms/widgets/time.html'
Membangun sebagai: <input type="text" ...>
Mengambil argumen sama seperti TextInput, dengan satu atau lebih argumen pilihan:
Bentuk dimana nilaiinisial bidang ini akan ditampilkan.
\nJika tidak ada argumen format disediakan, bentuk awalan adalah bentuk pertama ditemukan dalam TIME_INPUT_FORMATS dan menghormati Bentuk lokalisasi.
Untuk perlakuan dari mikro detik, lihat DateTimeInput.
TextareaLink to this heading#template_name: 'django/forms/widgets/textarea.html'
Membangun sebagai: <textarea>...</textarea>
Widget ini membuat penggunaan dari unsur-unsur HTML <select>, <input type="checkbox">, dan <input type="radio">.
Widgets that render multiple choices have an option_template_name attribute\nthat specifies the template used to render each choice. For example, for the\nSelect widget, select_option.html renders the <option> for a\n<select>.
CheckboxInputLink to this heading#input_type: 'checkbox'
template_name: 'django/forms/widgets/checkbox.html'
Membangun sebagai: <input type="checkbox" ...>
Mengambil satu argumen pilihan:
\nA callable that takes the value of the CheckboxInput and returns\nTrue if the checkbox should be checked for that value.
SelectLink to this heading#template_name: 'django/forms/widgets/select.html'
option_template_name: 'django/forms/widgets/select_option.html'
Membangun sebagai: <select><option ...>...</select>
This attribute is optional when the form field does not have a\nchoices attribute. If it does, it will override anything you set\nhere when the attribute is updated on the Field.
NullBooleanSelectLink to this heading#template_name: 'django/forms/widgets/select.html'
option_template_name: 'django/forms/widgets/select_option.html'
Pilih widget dengan pilihan 'Tidak dikenal', 'Ya' dan 'Tidak'
\nSelectMultipleLink to this heading#template_name: 'django/forms/widgets/select.html'
option_template_name: 'django/forms/widgets/select_option.html'
Mirip pada Select, tetai mengizinkan banyak pemilihan: <select multiple>...</select>
RadioSelectLink to this heading#template_name: 'django/forms/widgets/radio.html'
option_template_name: 'django/forms/widgets/radio_option.html'
Similar to Select, but rendered as a list of radio buttons within\n<div> tags:
<div>\n <div><input type="radio" name="..."></div>\n ...\n</div>\nFor more granular control over the generated markup, you can loop over the\nradio buttons in the template. Assuming a form myform with a field\nbeatles that uses a RadioSelect as its widget:
<fieldset>\n <legend>{{ myform.beatles.label }}</legend>\n {% for radio in myform.beatles %}\n <div class="myradio">\n {{ radio }}\n </div>\n {% endfor %}\n</fieldset>\nIni akan membangkitkan HTML berikut:
\n<fieldset>\n <legend>Radio buttons</legend>\n <div class="myradio">\n <label for="id_beatles_0"><input id="id_beatles_0" name="beatles" type="radio" value="john" required> John</label>\n </div>\n <div class="myradio">\n <label for="id_beatles_1"><input id="id_beatles_1" name="beatles" type="radio" value="paul" required> Paul</label>\n </div>\n <div class="myradio">\n <label for="id_beatles_2"><input id="id_beatles_2" name="beatles" type="radio" value="george" required> George</label>\n </div>\n <div class="myradio">\n <label for="id_beatles_3"><input id="id_beatles_3" name="beatles" type="radio" value="ringo" required> Ringo</label>\n </div>\n</fieldset>\nThat included the <label> tags. To get more granular, you can use each\nradio button's tag, choice_label and id_for_label attributes.\nFor example, this template...
<fieldset>\n <legend>{{ myform.beatles.label }}</legend>\n {% for radio in myform.beatles %}\n <label for="{{ radio.id_for_label }}">\n {{ radio.choice_label }}\n <span class="radio">{{ radio.tag }}</span>\n </label>\n {% endfor %}\n</fieldset>\n...akan menghasilkan HTML berikut:
\n<fieldset>\n <legend>Radio buttons</legend>\n <label for="id_beatles_0">\n John\n <span class="radio"><input id="id_beatles_0" name="beatles" type="radio" value="john" required></span>\n </label>\n <label for="id_beatles_1">\n Paul\n <span class="radio"><input id="id_beatles_1" name="beatles" type="radio" value="paul" required></span>\n </label>\n <label for="id_beatles_2">\n George\n <span class="radio"><input id="id_beatles_2" name="beatles" type="radio" value="george" required></span>\n </label>\n <label for="id_beatles_3">\n Ringo\n <span class="radio"><input id="id_beatles_3" name="beatles" type="radio" value="ringo" required></span>\n </label>\n</fieldset>\nIf you decide not to loop over the radio buttons -- e.g., if your template\nincludes {{ myform.beatles }} -- they'll be output in a <div> with\n<div> tags, as above.
The outer <div> container receives the id attribute of the widget,\nif defined, or BoundField.auto_id otherwise.
When looping over the radio buttons, the label and input tags include\nfor and id attributes, respectively. Each radio button has an\nid_for_label attribute to output the element's ID.
CheckboxSelectMultipleLink to this heading#template_name: 'django/forms/widgets/checkbox_select.html'
option_template_name: 'django/forms/widgets/checkbox_option.html'
Mirip pada SelectMultiple, tetapi dibangun sebagai daftar dari kotak centang:
<div>\n <div><input type="checkbox" name="..." ></div>\n ...\n</div>\nThe outer <div> container receives the id attribute of the widget,\nif defined, or BoundField.auto_id otherwise.
Like RadioSelect, you can loop over the individual checkboxes for the\nwidget's choices. Unlike RadioSelect, the checkboxes won't include the\nrequired HTML attribute if the field is required because browser validation\nwould require all checkboxes to be checked instead of at least one.
When looping over the checkboxes, the label and input tags include\nfor and id attributes, respectively. Each checkbox has an\nid_for_label attribute to output the element's ID.
FileInputLink to this heading#template_name: 'django/forms/widgets/file.html'
Membangun sebagai: <input type="file" ...>
ClearableFileInputLink to this heading#template_name: 'django/forms/widgets/clearable_file_input.html'
Membangun sebagai: <input type="file" ...> dengan masukan kotak centang tambahan untuk membersihkan nilai bidang, jika bidang tidak diwajibkan dan mempunyai data inisial.
SplitDateTimeWidgetLink to this heading#template_name: 'django/forms/widgets/splitdatetime.html'
Wrapper (using MultiWidget) around two widgets: DateInput\nfor the date, and TimeInput for the time. Must be used with\nSplitDateTimeField rather than DateTimeField.
SplitDateTimeWidget mempunyai beberapa argumen pilihan:
Mirip ke DateInput.format
Mirip ke TimeInput.format
Similar to Widget.attrs. A dictionary containing HTML\nattributes to be set on the rendered DateInput and\nTimeInput widgets, respectively. If these attributes aren't\nset, Widget.attrs is used instead.
SelectDateWidgetLink to this heading#template_name: 'django/forms/widgets/select_date.html'
Pembungkus disekitar tiga widget Select: satu untuk bulan, hari dan tahun.
Mengambil beberapa argumen pilihan:
\nAn optional list/tuple of years to use in the "year" select box.\nThe default is a list containing the current year and the next 9 years.
\nAn optional dict of months to use in the "months" select box.
\nThe keys of the dict correspond to the month number (1-indexed) and\nthe values are the displayed months:
\nMONTHS = {\n 1: _("jan"),\n 2: _("feb"),\n 3: _("mar"),\n 4: _("apr"),\n 5: _("may"),\n 6: _("jun"),\n 7: _("jul"),\n 8: _("aug"),\n 9: _("sep"),\n 10: _("oct"),\n 11: _("nov"),\n 12: _("dec"),\n}\nJika DateField tidak diwajibkan, SelectDateWidget akan memiliki pilihan kosong pada atas dari daftar (yaitu --- secara awalan). Anda dapat merubah tekas dari label ini dengan atribut empty_label. empty_label dapat berupa sebuah string, list, atau tuple. Ketika sebuah string digunakan, semua kotak-kotak pilihan akan setiapnya memiliki sebuah pilihan kosong dengan label ini. Jika empty_label adalah sebuah list atau tuple dari 3 unsur string, kotak-kotak pilihan akan memiliki label penyesuaian mereka sendiri. Label harus dalam urutan ini ('year_label', 'month_label', 'day_label').
# A custom empty label with string\nfield1 = forms.DateField(widget=SelectDateWidget(empty_label="Nothing"))\n\n# A custom empty label with tuple\nfield1 = forms.DateField(\n widget=SelectDateWidget(\n empty_label=("Choose Year", "Choose Month", "Choose Day"),\n ),\n)\n