cpython.git - https://github.com/python/cpython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fixed memory leak.	Hirokazu Yamamoto	2009-03-03	1	-2/+12
\|
*	- Issue #3745: Fix hashlib to always reject unicode and non buffer-api	Gregory P. Smith	2009-02-13	1	-16/+30
\| \| \| \| \| \|	supporting objects as input no matter how it was compiled (built in implementations or external openssl library). (backported from a py3k branch)
*	This reverts r63675 based on the discussion in this thread:	Gregory P. Smith	2008-06-09	1	-5/+5
\| \| \| \| \| \| \|	http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
*	Renamed PyString to PyBytes	Christian Heimes	2008-05-26	1	-5/+5
\|
*	#1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵	Christian Heimes	2007-12-19	1	-2/+2
\| \| \| \|	Py_REFCNT. Macros for b/w compatibility are available.
*	email address update	Gregory P. Smith	2007-09-09	1	-1/+1
\|
*	PEP 3123: Provide forward compatibility with Python 3.0, while keeping	Martin v. Löwis	2007-07-21	1	-6/+4
\| \| \| \| \|	backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
*	Make use of METH_O and METH_NOARGS where possible.	Georg Brandl	2006-05-29	1	-17/+7
\| \| \| \|	Use Py_UnpackTuple instead of PyArg_ParseTuple where possible.
*	Patch #1492356: Port to Windows CE (patch set 1).	Martin v. Löwis	2006-05-22	1	-99/+99
\|
*	Revert backwards-incompatible const changes.	Martin v. Löwis	2006-02-27	1	-2/+2
\|
*	Check return result from Py_InitModule*(). This API can fail.	Neal Norwitz	2006-01-19	1	-0/+2
\| \| \| \|	Probably should be backported.
*	Added the 'ULL' prefix to the unsigned long long literal constants.	Armin Rigo	2005-12-14	1	-99/+99
\| \| \| \|	Supresses numerous pages of compiler warnings.
*	Add const to several API functions that take char *.	Jeremy Hylton	2005-12-10	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char ; but if the type was created by type_new(), we know it is safe to cast to char *.
*	Remove the C99 "ULL" suffix from the 64bit unsigned long constants.	Gregory P. Smith	2005-08-23	1	-99/+99
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	VC++6 doesn't accept them. This will result in tons of the following warning from gcc 3.x: (gcc "2.96ish" doesn't issue this warning) warning: integer constant is too large for "long" type the code compiles fine regardless. squashing the gcc warnings is the next task. Would someone on windows please confirm that this does or does not compile and if it does or does not pass the test_hashlib.py unit tests.
*	[ sf.net patch # 1121611 ]	Gregory P. Smith	2005-08-21	1	-0/+777
	A new hashlib module to replace the md5 and sha modules. It adds support for additional secure hashes such as SHA-256 and SHA-512. The hashlib module uses OpenSSL for fast platform optimized implementations of algorithms when available. The old md5 and sha modules still exist as wrappers around hashlib to preserve backwards compatibility.