[issue23645] Incorrect doc for __getslice__

2015-03-13 Thread Gaëtan de Menten
Gaëtan de Menten added the comment: Thanks for creating the patch! PS: I know it is deprecated. But I am stuck on Python2 for that project and my class inherits from numpy ndarray, so I do not have a choice... -- ___ Python tracker <h

[issue23645] Incorrect doc for __getslice__

2015-03-12 Thread Gaëtan de Menten
New submission from Gaëtan de Menten: The documentation for __getslice__ at https://docs.python.org/2/reference/datamodel.html#object.__getslice__ states: "Note that missing i or j in the slice expression are replaced by zero or sys.maxint, respectively." However, in practice, it

[issue17559] str.is* implementation seem suboptimal for single character strings

2013-03-28 Thread Gaëtan de Menten
Gaëtan de Menten added the comment: Argl. I know I should have used 3.4... but that is what I thought I did. I used http://hg.python.org/cpython then "browse", and assumed it was the default branch... I know realize that since the last commit at that time was on the 2.7 branch, that

[issue17559] str.is* implementation seem suboptimal for single character strings

2013-03-27 Thread Gaëtan de Menten
New submission from Gaëtan de Menten: In isspace, isalpha, isalnum and isdigit, I see code like: /* Shortcut for single character strings */ if (PyString_GET_SIZE(self) == 1 && isspace(*p)) return PyBool_FromLong(1); Is it intentional to not use: if (PyString_GET_SIZE(se

[issue1202] zlib.crc32() and adler32() return value

2009-04-20 Thread Gaëtan de Menten
Gaëtan de Menten added the comment: Regarding the issue J. David Ibáñez has, I have a few comments to add: - It's also present on 32bit. - AFAICT: * it's present in both 2.6 branch & trunk (as of 68886), * it's a problem with line 1110 (in 2.6 branch), or line 1122 in