id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
37178	Move MiddlewareMixin out of utils.deprecation	Jacob Walls	CharulL00	"Following some mastodon [https://mastodon.social/@farhanaliraza/115418201200232304 chatter] kicked off by Farhan last fall, Carlton [https://discord.com/channels/856567261900832808/1430567236271079474/1430587741539668020 replied] with an answer about why `MiddlewareMixin` lives under `utils.deprecation`:

> I think it was meant to go away as we all moved to function based middleware. Then that never  happened. Then MiddlewareMixin grew the async adaption two-step, and it’s useful for that. Even if we just use it internally, it should probably be moved. (Clean code and all that Jazz)

We have some +1s on that Mastodon thread, ending with ""if a fellow picks it up"", so here I am, proposing to move it :-)

We could choose to leave a single alias in `utils.deprecation` to avoid breaking changes for people explicitly importing `MiddlewareMixin`. It's a lot simpler than adding a release note or a deprecation path. (I might be in the minority with this view, though.)"	Cleanup/optimization	assigned	HTTP handling	dev	Normal			Farhan Ali Jake Howard Carlton Gibson	Accepted	0	0	0	0	1	0