Gregory P. Smith a6be61ec71 Keep y a Py_hash_t instead of Py_uhash_t as it is compared with == -1 and the ... compiler logic will do the right thing with just x as a Py_uhash_t. This matches what was already done in the 3.3 version. cleanup only - no functionality or hash values change.		2012-12-10 18:34:09 -08:00
..
stringlib
abstract.c
accu.c
boolobject.c
bytearrayobject.c	Fix compilation on Windows	2012-11-03 23:07:59 +01:00
bytes_methods.c
bytesobject.c	Fix the internals of our hash functions to used unsigned values during hash	2012-12-10 18:15:46 -08:00
capsule.c
cellobject.c
classobject.c
codeobject.c
complexobject.c
descrobject.c
dictnotes.txt
dictobject.c	avoid a function call with redundant checks for dict size	2012-10-31 14:22:12 -04:00
enumobject.c
exceptions.c
fileobject.c
floatobject.c
frameobject.c
funcobject.c
genobject.c
iterobject.c
listobject.c
listsort.txt
lnotab_notes.txt
longobject.c
memoryobject.c
methodobject.c
moduleobject.c
object.c
obmalloc.c
rangeobject.c	Issue #16402: In range slicing, fix shadowing of exceptions from __index__ method.	2012-11-04 11:46:17 +00:00
setobject.c	Fix the internals of our hash functions to used unsigned values during hash	2012-12-10 18:15:46 -08:00
sliceobject.c
structseq.c
tupleobject.c	Keep y a Py_hash_t instead of Py_uhash_t as it is compared with == -1 and the	2012-12-10 18:34:09 -08:00
typeobject.c
typeslots.inc
typeslots.py
unicodectype.c
unicodeobject.c	Fix the internals of our hash functions to used unsigned values during hash	2012-12-10 18:15:46 -08:00
unicodetype_db.h
weakrefobject.c	Issue #16602: When a weakref's target was part of a long deallocation chain, the object could remain reachable through its weakref even though its refcount had dropped to zero.	2012-12-08 21:15:26 +01:00