diff options
| author | Paul Kehrer <paul.l.kehrer@gmail.com> | 2014-03-24 19:25:02 -0430 |
|---|---|---|
| committer | Paul Kehrer <paul.l.kehrer@gmail.com> | 2014-03-24 19:25:02 -0430 |
| commit | 8573916ba3ea3b403f51ec4de4051db09fa91cda (patch) | |
| tree | a56661e8b5df1377e9a59c6a72a70e12fef97e57 /docs | |
| parent | eb98d47b925071acb3f0b1df6146a533525520fc (diff) | |
| parent | 3888a84c2b7fc45adf3fa665880d554c1766165e (diff) | |
| download | cryptography-8573916ba3ea3b403f51ec4de4051db09fa91cda.tar.gz cryptography-8573916ba3ea3b403f51ec4de4051db09fa91cda.tar.bz2 cryptography-8573916ba3ea3b403f51ec4de4051db09fa91cda.zip | |
Merge pull request #795 from public/split-vectors
Split vectors into cryptography_vectors
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/development/test-vectors.rst | 12 | ||||
| -rw-r--r-- | docs/doing-a-release.rst | 4 |
2 files changed, 12 insertions, 4 deletions
diff --git a/docs/development/test-vectors.rst b/docs/development/test-vectors.rst index 164d0abd..c5ea8152 100644 --- a/docs/development/test-vectors.rst +++ b/docs/development/test-vectors.rst @@ -2,10 +2,14 @@ Test vectors ============ Testing the correctness of the primitives implemented in each ``cryptography`` -backend requires trusted test vectors. Where possible these vectors are obtained -from official sources such as `NIST`_ or `IETF`_ RFCs. When this is not possible -``cryptography`` has chosen to create a set of custom vectors using an official -vector file as input to verify consistency between implemented backends. +backend requires trusted test vectors. Where possible these vectors are +obtained from official sources such as `NIST`_ or `IETF`_ RFCs. When this is +not possible ``cryptography`` has chosen to create a set of custom vectors +using an official vector file as input to verify consistency between +implemented backends. + +Vectors are kept in the `cryptography_vectors` package rather than within our +main test suite. Sources ------- diff --git a/docs/doing-a-release.rst b/docs/doing-a-release.rst index 8b37df78..fc88a91c 100644 --- a/docs/doing-a-release.rst +++ b/docs/doing-a-release.rst @@ -10,6 +10,7 @@ The first step in doing a release is bumping the version number in the software. * Update the version number in ``cryptography/__about__.py``. +* Update the version number in ``vectors/cryptography_vectors/__about__.py``. * Set the release date in the :doc:`/changelog`. * Do a commit indicating this. * Send a pull request with this. @@ -33,5 +34,8 @@ correctly: >>> import cryptography >>> cryptography.__version__ '...' + >>> import cryptography_vectors + >>> cryptography_vectors.__version__ + '...' Verify that this is the version you just released. |