delta/python-packages/cryptography.git/src/cryptography/exceptions.py, branch 0.9.1 github.com: pyca/cryptography.git InvalidToken is deprecated in 09, not 08 2015-04-13T22:20:47+00:00 Steven Buss steven.buss@gmail.com 2015-04-13T19:38:59+00:00 b3f45e3b16990a9293f68faecde3da790e4a4216 






Move cryptography.exceptions.InvalidToken to cryptography.hazmat.primitives.twofactor
2015-04-13T22:20:47+00:00

Steven Buss
steven.buss@gmail.com

2015-04-13T17:35:50+00:00

e079c554e7b3506dfd8be56b2fd20336c79ce7a0












made the internal _Reasons an enum, since we already depend on enum34
2014-12-19T03:27:36+00:00

Alex Gaynor
alex.gaynor@gmail.com

2014-12-19T03:27:36+00:00

01aa770768e8dcb1c776c7b869d2ec050bf8010b

fixes #854





fixes #854







add X509Backend support to multibackend
2014-11-27T03:06:02+00:00

Paul Kehrer
paul.l.kehrer@gmail.com

2014-11-26T19:55:40+00:00

ae8156f1812c28e0265ed3215291be469aa4fd05












Update the license header for every source file, as well as the documentation.
2014-11-16T17:08:42+00:00

Alex Gaynor
alex.gaynor@gmail.com

2014-11-16T17:08:42+00:00

5951f46be60095a74546b318432417e51bfe0aab

Fixes #1209





Fixes #1209







Move the cryptography package into a src/ subdirectory
2014-11-13T12:56:31+00:00

Donald Stufft
donald@stufft.io

2014-11-08T00:17:08+00:00

c62a78c015cf7aeb0c05bce82ef14cd86fe0b0fc

Due to differences in how py.test determines which module to ``import``
the test suite actually runs against the cryptography which is in the
*current* directory instead of the cryptography which is installed. The
problem essentially boils down to when there is a tests/__init__.py then
py.test adds the current directory to the front of the sys.path, causing
it to take precedence over the installed location.

This means that running the tests relies on the implicit compile
that CFFI does instead of testing against what people will actually
be runnning, which is the module compiled by setup.py.





Due to differences in how py.test determines which module to ``import``
the test suite actually runs against the cryptography which is in the
*current* directory instead of the cryptography which is installed. The
problem essentially boils down to when there is a tests/__init__.py then
py.test adds the current directory to the front of the sys.path, causing
it to take precedence over the installed location.

This means that running the tests relies on the implicit compile
that CFFI does instead of testing against what people will actually
be runnning, which is the module compiled by setup.py.