cloud-email/cryptography - python cryptography

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add flag to toggle key length check for HOTP and TOTP. (#3012)	Terry Chia	2016-07-16	2	-4/+6
\| \| \| \| \| \| \| \| \| \|	* Add an enforce_key_length parameter to HOTP and TOTP. * Document changes in docs. * Add some words to the wordlist. * Add versionadded to docs.
*	Change ' to ".	Terry Chia	2015-06-19	3	-12/+12
\|
*	add license header and fix grammar errors.	Jiangge Zhang	2015-06-03	1	-0/+4
\|
*	Remove a default argument and rename a private function.	Jiangge Zhang	2015-06-03	3	-8/+8
\|
*	Follow the review advice: turn URI generator into methods.	Jiangge Zhang	2015-06-03	3	-27/+15
\|
*	Add "generate_key_uri" utility for HOTP/TOTP.	Jiangge Zhang	2015-05-26	1	-0/+50
\|
*	Move cryptography.exceptions.InvalidToken to ↵	Steven Buss	2015-04-13	3	-2/+8
\| \| \| \|	cryptography.hazmat.primitives.twofactor
*	Update the license header for every source file, as well as the documentation.	Alex Gaynor	2014-11-16	3	-36/+9
\| \| \| \|	Fixes #1209
*	Move the cryptography package into a src/ subdirectory	Donald Stufft	2014-11-13	3	-0/+124
	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.