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

	Commit message (Collapse)	Author	Age	Files	Lines
*	#3935: properly support list subclasses in the C impl. of bisect.	Georg Brandl	2008-10-08	1	-2/+2
\| \| \| \|	Patch reviewed by Raymond.
*	Finish conversion from int to Py_ssize_t.	Raymond Hettinger	2008-07-24	1	-23/+23
\|
*	Issue 3301: Bisect functions behaved badly when lo was negative.	Raymond Hettinger	2008-07-10	1	-0/+8
\|
*	More unconsting.	Martin v. Löwis	2006-02-27	1	-4/+4
\|
*	Use Py_ssize_t for counts and sizes.	Martin v. Löwis	2006-02-16	1	-2/+2
\|
*	Add const to several API functions that take char *.	Jeremy Hylton	2005-12-10	1	-5/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 *.
*	SF #1313496: bisect C replacement doesn't accept named args	Raymond Hettinger	2005-10-05	1	-22/+26
\|
*	Any call to insort_{left,right} with a non-list leaked a reference to None	Michael W. Hudson	2004-08-02	1	-6/+10
\| \| \| \|	(or to whatever the 'insert' method chose to return).
*	SF Patch #864863: Bisect C implementation	Raymond Hettinger	2004-01-05	1	-0/+228
	(Contributed by Dmitry Vasiliev.)