#37178: Move MiddlewareMixin out of utils.deprecation
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Type:
| Cleanup/optimization
Status: new | Component: HTTP
| handling
Version: dev | Severity: Normal
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
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.)
--
Ticket URL: <https://code.djangoproject.com/ticket/37178>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019edb204612-0333a564-48d6-4ea4-a8f9-a098bb72aa8d-000000%40eu-central-1.amazonses.com.
