delta/python-packages/pycrypto.git - github.com: dlitz/pycrypto.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix tests when running under "python -OO" (PYTHONOPTIMIZE set to 1 or 2)	Dwayne Litzenberger	2014-06-22	1	-2/+4
\|
*	Merge from upstream	Legrandin	2011-12-22	1	-3/+3
\|\
\| *	Python 3.x fixes:	Dwayne C. Litzenberger	2011-10-22	1	-3/+3
\| \| \| \| \| \| \| \| \| \|	- Use absolute imports - Fix StringIO import so that 2to3 can translate it
* \|	Merged from upstream (py3k support) and modified so that all unit tests pass.	Legrandin	2011-10-18	3	-21/+28
\|\ \ \| \|/
\| *	Unwraping byte conversion on test vectors.	Anders Sundman	2011-04-24	2	-11/+11
\| \| \| \| \| \| \| \|	Doing the wraping later, at the point of use instead.
\| *	PY3K _fastmath support	Thorsten Behrens	2010-12-29	2	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	o _fastmath now builds and runs on PY3K o Changes to setup.py to allow /usr/include for gmp.h o Changes to setup.py to allow linking fastmath w/ static mpir on Windows without warning messages o Changes to test_DSA/test_RSA to throw an exception if _fastmath is present but cannot be imported (due to an issue building _fastmath or the shared gmp/mpir libraries not being reachable) o number.py has the code to flag a failing _fastmath, but that code is commented out for a better runtime experience o Clean up the if for py21compat import - should have been == not is o Clean up some '== None' occurences, now 'is None' instead
\| *	Changes to allow pycrpyto to work on Python 3.x as well as 2.1 through 2.7	Thorsten Behrens	2010-12-28	3	-27/+34
\| \|
* \|	Added Lorenz Quack's native C implementation of all SHA-2 algorithm	Legrandin	2011-10-16	1	-1/+1
\|/ \| \| \| \| \| \| \| \|	(as submitted here https://bugs.launchpad.net/pycrypto/+bug/544792) so that they are available also in Python 2.1, 2.2, 2.3 and 2.4. Regardless where the implementation comes from (Python standard library or our native modules, depending on the Python version), all Crypto.Hash objects are always used as front-ends.
*	Legal: Dedicate my files to the public domain.	Dwayne C. Litzenberger	2009-03-01	4	-84/+68
\| \| \| \| \| \| \| \| \| \| \| \| \|	In an attempt to simplify the copyright status of PyCrypto, I'm placing my code into the public domain, and encouraging other contributors to do the same. I have used a public domain dedication that was recommended in a book on FOSS legal issues[1], followed by the warranty disclaimer boilerplate from the MIT license. [1] _Intellectual Property and Open Source: A Practical Guide to Protecting Code_, a book written by Van Lindberg and published by O'Reilly Media. (ISBN 978-0-596-51796-0)
*	cleanup: Move modules to "lib/Crypto" subdirectory.	Dwayne C. Litzenberger	2009-02-28	4	-0/+380
	This will avoid the previous situation where scripts like the old "test.py" get included accidentally in a release. It also frees us to put additional build scripts in the top-level directory of the source tree.