cloud-email/cryptography - python cryptography

	Commit message (Collapse)	Author	Age	Files	Lines
...
* \|	change the cfdataref typedef to be more flexible/correct	Paul Kehrer	2014-11-24	1	-1/+1
\| \|
* \|	add SecItemExport binding	Paul Kehrer	2014-11-24	1	-0/+2
\| \|
* \|	Merge pull request #1488 from alex/no-sslv3	Paul Kehrer	2014-11-24	1	-0/+16
\|\ \ \| \| \| \| \| \|	Support compilation on platforms, such as debian expiremental, which are compiled without SSLv3
\| * \|	Support compilation on platforms, such as debian expiremental, which are ↵	Alex Gaynor	2014-11-24	1	-0/+16
\| \|/ \| \| \| \| \| \|	compiled without SSLv3
* /	Don't check DSA error stack	Alex Stapleton	2014-11-24	1	-5/+1
\|/
*	Update the license header for every source file, as well as the documentation.	Alex Gaynor	2014-11-16	96	-1153/+289
\| \| \| \|	Fixes #1209
*	Monkeypatch the CFFI Verifier to prevent the implicit compile	Donald Stufft	2014-11-14	1	-0/+11
\|
*	Move the cryptography package into a src/ subdirectory	Donald Stufft	2014-11-13	96	-0/+12481
	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.