summaryrefslogtreecommitdiffstats
path: root/Modules/sha1module.c
Commit message (Collapse)AuthorAgeFilesLines
* Fixed memory leak on failure. This is related to issue5403 but won't crash ↵Hirokazu Yamamoto2009-03-031-2/+7
| | | | on py3k.
* Fixes Issue #3745: Fix hashlib to always reject unicode and nonGregory P. Smith2009-02-121-5/+12
| | | | | buffer-api supporting objects as input no matter how it was compiled (built in implementations or external openssl library).
* Issue #1717: rename tp_compare to tp_reserved. I'll change theMark Dickinson2009-02-021-1/+1
| | | | | type of tp_compare in a separate commit, for ease of reversion should things go wrong.
* Zero-initialize buf. Fixes #3557.Martin v. Löwis2008-08-151-0/+1
|
* Use s* to receive data. Fixes #3552.Martin v. Löwis2008-08-141-10/+11
|
* Fix module initialization glitches.Martin v. Löwis2008-06-111-2/+0
|
* Implement PEP 3121: new module initialization and finalization API.Martin v. Löwis2008-06-111-5/+16
|
* Renamed PyString to PyBytesChristian Heimes2008-05-261-1/+1
|
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and Py_REFCNT.Christian Heimes2007-12-191-2/+2
|
* Cleanup: Replaced most PyInt_ aliases with PyLong_ and disabled the aliases ↵Christian Heimes2007-12-021-2/+2
| | | | in intobject.h
* Merging the py3k-pep3137 branch back into the py3k branch.Guido van Rossum2007-11-061-1/+1
| | | | | | | | | | | | | | No detailed change log; just check out the change log for the py3k-pep3137 branch. The most obvious changes: - str8 renamed to bytes (PyString at the C level); - bytes renamed to buffer (PyBytes at the C level); - PyString and PyUnicode are no longer compatible. I.e. we now have an immutable bytes type and a mutable bytes type. The behavior of PyString was modified quite a bit, to make it more bytes-like. Some changes are still on the to-do list.
* Adds stand alone _md5 and _sha1 modules for use by hashlib on systemsGregory P. Smith2007-09-091-0/+537
when the OpenSSL library is either not present or not found by setup.py. These are derived from the public domain libtomcrypt (libtom.org) just like the existing sha256 and sha512 modules.