[Python-Dev] Let's stop eating exceptions in dict lookup (original) (raw)
Guido van Rossum guido at python.org
Tue May 30 05:23:29 CEST 2006
- Previous message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Next message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/29/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Fredrik Lundh wrote:
> well, the empty string is a valid substring of all possible strings > (there are no "null" strings in Python). you get the same behaviour > from slicing, the "in" operator, "replace" (this was discussed on the > list last week), "count", etc. Although Tim pointed out that replace() only regards n+1 empty strings as existing in a string of lenth n. So for consistency, find() should only find them in those places, too.
And "abc".count("") should return 4.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Next message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]