Anymail switched to use SendGrid's newer v3 API in February, 2017 (Anymail v0.8). But the older SendGrid v2 API remained available as an option.
In the interest of reducing maintenance overhead, I'm proposing dropping support for SendGrid v2 in a near-future release.
If you are using Anymail with SendGrid v2 and cannot switch to the default v3 API, please comment. (This affects you if your Django settings have EMAIL_BACKEND = "anymail.backends.sendgrid_v2.EmailBackend".)
In particular, if you must use SENDGRID_USERNAME/SENDGRID_PASSWORD authentication, rather than SENDGRID_API_KEY as required by their v3 API, I'd like to better understand that use case before finalizing this decision.
Anymail switched to use SendGrid's newer v3 API in February, 2017 (Anymail v0.8). But the older SendGrid v2 API remained available as an option.
In the interest of reducing maintenance overhead, I'm proposing dropping support for SendGrid v2 in a near-future release.
If you are using Anymail with SendGrid v2 and cannot switch to the default v3 API, please comment. (This affects you if your Django settings have
EMAIL_BACKEND = "anymail.backends.sendgrid_v2.EmailBackend".)In particular, if you must use SENDGRID_USERNAME/SENDGRID_PASSWORD authentication, rather than SENDGRID_API_KEY as required by their v3 API, I'd like to better understand that use case before finalizing this decision.