Closed medmunds closed 5 months ago
[Split into two commits, which makes it possible to see the actual diffs in the renamed files before adding the compatibility versions on the original filenames: backends/sendinblue.py → backends/brevo.py; webhooks/sendinblue.py → webhooks/brevo.py]
(Released in Anymail 10.3)
I've been rethinking my arguments in #321 about leaving "SendinBlue" in the code while calling it "Brevo" everywhere else. I now feel this creates more confusion (particularly with new users) than it avoids.
This PR renames "sendinblue" to "brevo" throughout the code, but maintains compatibility versions on the old names and URLs (with deprecation warnings).
The compatibility versions use the old
esp_name
, which means that settings names and other related features are also unchanged. So if you haveEMAIL_BACKEND = "…sendinblue.EmailBackend"
, Anymail will continue to look forSENDINBLUE_API_KEY
in the settings. But when you update toEMAIL_BACKEND = "…brevo.EmailBackend"
, you'll need to switch toBREVO_API_KEY
at the same time.I don't have any particular schedule for removing the deprecated compatibility versions. (They don't really add maintenance overhead.)