DecimalField and settings.USE_L10N

[cocorocho]

Hello,

According to documentation, DecimalField localizes value based on either localize argument or settings.USE_L10N.

DecimalField
localize - Set to True to enable localization of input and output based on the current locale. This will also force coerce_to_string to True. Defaults to False. Note that data formatting is enabled if you have set USE_L10N=True in your settings file.

So my USE_L10N is set to True and my DecimalField(s) are still not localized. Then I looked at the source code for DecimalField and realized that USE_L10N has no effect at all.

django-rest-framework/rest_framework/fields.py

Lines 962 to 978 in 4abfa28

	class DecimalField(Field):
	default_error_messages = {
	'invalid': _('A valid number is required.'),
	'max_value': _('Ensure this value is less than or equal to {max_value}.'),
	'min_value': _('Ensure this value is greater than or equal to {min_value}.'),
	'max_digits': _('Ensure that there are no more than {max_digits} digits in total.'),
	'max_decimal_places': _('Ensure that there are no more than {max_decimal_places} decimal places.'),
	'max_whole_digits': _('Ensure that there are no more than {max_whole_digits} digits before the decimal point.'),
	'max_string_length': _('String value too large.')
	}
	MAX_STRING_LENGTH = 1000 # Guard against malicious string inputs.
	def __init__(self, max_digits, decimal_places, coerce_to_string=None, max_value=None, min_value=None,
	localize=False, rounding=None, normalize_output=False, **kwargs):
	self.max_digits = max_digits
	self.decimal_places = decimal_places
	self.localize = localize

I would expect

django-rest-framework/rest_framework/fields.py

Line 978 in 4abfa28

self.localize = localize

to be

self.localize = getattr(settings, "USE_L10N", localize)

then it would work as documented.

Hence I forked in order to create a pull request, then I noticed that USE_L10N is going to be deprecated in Django 5.0.

I haven't checked the previous commits, but is the current state intended due to upcoming deprecation of USE_L10N?

If it is, we are currently on Django 4.16 isn't it too soon, if it is not then the documentation is misleading?

If none of the above, then I can gladly make a pull request if it is needed.

Thanks!