mirror of
https://github.com/pacnpal/django-anymail.git
synced 2025-12-20 03:41:05 -05:00
Docs: update tooling and outdated/broken content
* Update docs build config
* Specify Sphinx and theme versions in docs/requirements.txt
(tox had been using latest; RTD had pinned older versions)
* Update docs builds for Python 3 and recent Sphinx
* Remove obsolete sphinx-rtd-theme patches
* Add .readthedocs.yml
* Move some JS to async (now that Sphinx supports that)
* Fix version-alert.js for async loading
* Remove docs versionadded/changed info older than v3.0
* Fix broken GitHub issue links in changelog (never worked?)
* Add setup long_description_content_type
* Drop poorly maintained AUTHORS.txt
(just point to GitHub contributors page)
This commit is contained in:
@@ -282,20 +282,11 @@ This is actually implemented using HTTP basic authentication, and the string is
|
||||
technically a "username:password" format. But you should *not* use any real
|
||||
username or password for this shared secret.
|
||||
|
||||
.. versionchanged:: 1.4
|
||||
|
||||
The earlier WEBHOOK_AUTHORIZATION setting was renamed WEBHOOK_SECRET, so that
|
||||
Django error reporting sanitizes it. Support for the old name was dropped in
|
||||
Anymail 2.0, and if you have not yet updated your settings.py, all webhook calls
|
||||
will fail with a "missing or invalid basic auth" error.
|
||||
|
||||
|
||||
.. setting:: ANYMAIL_REQUESTS_TIMEOUT
|
||||
|
||||
.. rubric:: REQUESTS_TIMEOUT
|
||||
|
||||
.. versionadded:: 1.3
|
||||
|
||||
For Requests-based Anymail backends, the timeout value used for all API calls to your ESP.
|
||||
The default is 30 seconds. You can set to a single float, a 2-tuple of floats for
|
||||
separate connection and read timeouts, or `None` to disable timeouts (not recommended).
|
||||
|
||||
Reference in New Issue
Block a user