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.

This seems like it could be a pretty reasonable change to me, along with a major version bump.

Granted there's probably some codebases that might be forced into a change, OTOH, itis an argument that makes much more sense as a keyword-only case.

Any other maintainers have an opinion on the trade-off here?

I like it! This avoids a problem known as "the boolean trap".

It like it too, but it breaks the existing API and changelog doesn't mention that :(

It's inhttps://www.django-rest-framework.org/community/3.14-announcement/ andhttps://www.django-rest-framework.org/community/release-notes/

But yes, upgrades that break thingsare a pain. Even when we want them.

OK, then it would make sense to include a link to the former in the latter, as originally I only found and read the latter (as I was reviewing tons of changelogs for multiple packages which got updated for my project). Additionally I'd suggest explicitly marking breaking changes with some prefix / tag / whatever ("BREAKING: ...") to make sure no one will miss that. Anyway, keep up the good work!