Document that urlpatterns can be a sequence object.

[Batuhan Taşkaya]

Why urlpatterns has to be a *Python list*? Doesn't all sequences (an object that implements collections.abc.Sequence interface) counts for that. IMO this description should change at url dispatching page. As a real example i'm using collections.UserList based pattern manager for it (can be found in ​here)

[Mariusz Felisiak]

Agreed, we can clarify this in ​syntax-of-the-urlpatterns-variable, e.g. "... should be an iterable (e.g. a list or tuple) of ..."

[Jonatas CD]

​PR created.

[Marten Kenbeek]

Note that it can't be any iterable: it has to be a sequence (implement __getitem__() and __len__()) or otherwise implement __reversed__(). reversed() is called in the patterns when building the reverse url patterns.

[Mariusz Felisiak]

Thanks for pointing this. You're right we should be more precise.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 8aad3321:

Fixed #30437 -- Clarified that urlpatterns can be a sequence.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 72fe36c2:

[2.2.x] Fixed #30437 -- Clarified that urlpatterns can be a sequence.

Backport of 8aad3321ed6f0b603361767a4fe00d046b5fdd34 from master