Hi Mike,
overall the plan sounds good. I especially like the approach to "fix" the
tests first. This can happen in an extra merge request and reviewed
independently so we can be sure that we are still testing what we want to
test before moving to the tricky parts.
On Thursday, June 27, 2024 at 3:28:06 AM UTC+2 Mike Edmunds wrote:
1.
Deprecate unused internal APIs from django.core.mail.message
Django will no longer need these (Python's modern email API covers their
functionality), but they may be in use by third-party libraries:
- utf8_charset
- utf8_charset_qp
- RFC5322_EMAIL_LINE_LENGTH_LIMIT
- BadHeaderError^ (more details below)
- ADDRESS_HEADERS
- forbid_multi_line_headers()^
- sanitize_address() (more details below)
- MIMEMixin
- SafeMIMEMessage
- SafeMIMEText^
- SafeMIMEMultipart^
(Items marked ^ are exposed in django.core.mail via __all__. I haven't
looked into the reason for that.)
Are all of those documented? If not we can simply remove them (especially
if the deprecation implementation turns out to be a PITA).
Cheers,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/df3db456-b847-416b-b496-b6e70e824fc7n%40googlegroups.com.
