summaryrefslogtreecommitdiffstats
path: root/Python/pythonrun.c
diff options
context:
space:
mode:
authorMoshe Zadka <moshez@math.huji.ac.il>2001-04-11 08:06:02 (GMT)
committerMoshe Zadka <moshez@math.huji.ac.il>2001-04-11 08:06:02 (GMT)
commit097cf85daec73d386768d1d49947c470d59cf578 (patch)
tree570e3154b20c6f6279c71a760e880fa05ec2bf5a /Python/pythonrun.c
parentabbae5b3ccfbb5914a894fd9d9a0e1e1d900bd86 (diff)
downloadcpython-097cf85daec73d386768d1d49947c470d59cf578.zip
cpython-097cf85daec73d386768d1d49947c470d59cf578.tar.gz
cpython-097cf85daec73d386768d1d49947c470d59cf578.tar.bz2
Inspired by Tim Peters' 1.14->1.15 checkin to asynchat
Quoting orignal message: ''' Fix from the Madusa mailing list: http://groups.yahoo.com/group/medusa/message/333 It's clear that Medusa should not be checking for an empty buffer via "buf is ''". The patch merely changes "is" to "==". However, there's a mystery here all the same: Python attempts to store null strings uniquely, so it's unclear why "buf is ''" ever returned false when buf actually was empty. *Some* string operations produce non-unique null strings, e.g. '''
Diffstat (limited to 'Python/pythonrun.c')
0 files changed, 0 insertions, 0 deletions