The explanation ended in the middle.

[Joon Hwan 김준환]

​https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/fields/#range-fields
​https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/fields/#integerrangefield
​https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/fields/#bigintegerrangefield
​https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/fields/#daterangefield

You can see the sentence ends with "that is [)."

[Carlton Gibson]

This is how Postres ranges are specified. See ​https://www.postgresql.org/docs/9.3/rangetypes.html#RANGETYPES-IO

Wonder if we can explain that better.

[Mariusz Felisiak]

Yes, see ​https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-INCLUSIVITY.

We can only add ref to the PostgreSQL documentation like in ​RangeBoundary.

[Carlton Gibson]

Hmmm. We already link to the psycopg docs here: ​https://www.psycopg.org/docs/extras.html#adapt-range.

I'm going to say wontfix, as the [) is already marked out as a code literal. But if anyone wants to suggest a concrete clarification I'm happy to review.

[Joon Hwan 김준환]

I had difficulty reading the document because I didn't have any background knowledge of Range Boundary expression.
I carefully suggests putting the next link nearby Range Fields.
​https://docs.djangoproject.com/en/3.0/ref/contrib/postgres/fields/#rangeboundary-expressions

If you want, I will change it myself.

[Carlton Gibson]

A PR clarifying would be very welcome. Please assign yourself and reopen the ticket if you will provide one. Thanks!

[Joon Hwan 김준환]

Let me provide PR as soon as possible.

[Carlton Gibson]

OK, super. I shall Accept on that basis.

Thanks for the input! 🎉

[Joon Hwan 김준환]

​PR

[Mariusz Felisiak <felisiak.mariusz@…>]

In 4029bcd6:

Fixed #31577 -- Clarified docs about bounds of RangeFields.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 03bfcba:

[3.1.x] Fixed #31577 -- Clarified docs about bounds of RangeFields.

Backport of 4029bcd6b20f75a78f9a5829d7826c79aeb20732 from master