Properly handle OverflowError in DurationField deserialization

[peterthomassen]

Related: https://github.com/django/django/pull/8870/files

Note: Before submitting this pull request, please review our contributing guidelines.

Description

Properly handle OverflowError in DurationField deserialization. Solution is the same as for the corresponding Django form field.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[peterthomassen]

I think this is still current.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[peterthomassen]

I think this is still current.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[peterthomassen]

I think this is still current.

[auvipy]

we have recently merged an identical feature for another field #8725. can you cross check and make amendment accordingly to this PR?

[peterthomassen]

The code looks very similar to me. Which according amendments do you mean? (Would you like to change the logic, or the error message? (Number of days out of range, must be between {min_days} and {max_days}.)

[auvipy]

btw, having another look, it seems your code is quite right. can you please pull from master so that the CI triggers with latest changes?

[peterthomassen]

done

[auvipy]

thank you for your patience