Subclasses of django.contrib.postgres.forms.ranges.BaseRangeField should have more specific error messages

[Alexey Boriskin]

I was translating new contrib.postgres strings on transifex and noticed that all range fields use the same error message: "Enter two valid values".
I suppose it may be misleading for the user of those fields, as the type of those values is not explicitly specified.
I propose that each subclass of BaseRangeField - IntegerRangeField, FloatRangeField, etc. to have its own 'invalid' error message - e.g. "Enter two valid integers", "Enter two valid dates", etc.

[Tim Graham]

Any opinion on this, Marc?

[Marc Tamlyn]

I don't mind, seems like it's probably a good idea. There aren't any technical challenges. The same code of the ValidationError should be kept across all the fields.

[Chris Foresman]

I'll take a crack at this.

[Chris Foresman]

Tim,

Should these just be "integers", "floats", or something more humane? E.g. "Enter two valid whole numbers"?

[Chris Foresman]

Pull request open here: ​https://github.com/django/django/pull/4169

[Tim Graham <timograham@…>]

In 1d1d5d1c315e0e58f02a7f2a07b56ed20b09c087:

Fixed #24341 -- Added specific error messages to RangeField subclasses

[Tim Graham <timograham@…>]

In 3207fcd0a0b90e677b1bb5cf662dee21c659adab:

[1.8.x] Fixed #24341 -- Added specific error messages to RangeField subclasses

Backport of 1d1d5d1c315e0e58f02a7f2a07b56ed20b09c087 from master