From 872835ea0ded7a1a07ff025646c46bc29899b83f Mon Sep 17 00:00:00 2001 From: Paul Kehrer Date: Sun, 16 Aug 2020 14:23:02 -0500 Subject: update submitting patches docs to be a bit more true (#5407) For now best practice is that they should be optional. --- docs/development/submitting-patches.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/development') 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 ~~~~~~~~~~ -- cgit v1.2.1