summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPaul Kehrer <paul.l.kehrer@gmail.com>2020-08-16 14:23:02 -0500
committerGitHub <noreply@github.com>2020-08-16 15:23:02 -0400
commit872835ea0ded7a1a07ff025646c46bc29899b83f (patch)
tree22f5c30ef2767e1f63363fca1f146807f821b6e1 /docs
parent4a581a9e7080aaf802f7208ce66cd941336bfcf8 (diff)
downloadcryptography-872835ea0ded7a1a07ff025646c46bc29899b83f.tar.gz
update submitting patches docs to be a bit more true (#5407)
For now best practice is that they should be optional.
Diffstat (limited to 'docs')
-rw-r--r--docs/development/submitting-patches.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/development/submitting-patches.rst b/docs/development/submitting-patches.rst
index 11281b525..b4ed175e6 100644
--- a/docs/development/submitting-patches.rst
+++ b/docs/development/submitting-patches.rst
@@ -81,10 +81,9 @@ Every recipe should include a version or algorithmic marker of some sort in its
output in order to allow transparent upgrading of the algorithms in use, as
the algorithms or parameters needed to achieve a given security margin evolve.
-APIs at the :doc:`/hazmat/primitives/index` layer should always take an
-explicit backend, APIs at the recipes layer should automatically use the
-:func:`~cryptography.hazmat.backends.default_backend`, but optionally allow
-specifying a different backend.
+APIs at the :doc:`/hazmat/primitives/index` and recipes layer should
+automatically use the :func:`~cryptography.hazmat.backends.default_backend`,
+but optionally allow specifying a different backend.
C bindings
~~~~~~~~~~