These fixes are not agressive as some of the code is complicated and it is better to be careful. The files numeric.py and numerictypes.py are not easily analysed and the latter is self modifying. Pyflakes generates a number of invalid warnings for those files.
Most of these fixes involve putting blank lines around .. versionadded:: x.x.x and .. deprecated:: x.x.x Some of the examples were also fixed.
The lists needed blank lines before starting.
The proper reference is in routines.rst.
List needs to be preceded by blank line.
Rather than representing them as "-9223372036854775808", we now represent them as "'NaT'", as in datetime64 arrays. Note this changes the numpy.core.arrayprint printer, not the builtin printer.
Before this change, we defined a nb_matrix_multiply slot but not a nb_inplace_matrix_multiply slot, which means that a statement like a @= b would be silently expanded by the CPython interpreter to become a = a @ b This is undesireable, because it produces unexpected memory allocations, breaks view relationships, and so forth. This commit adds a nb_inplace_matrix_multiply slot which simply errors out, and suggests that users write 'a = a @ b' explicitly if that's what they want.
Filed upstream as: nose-devs/nose#929 Not our problem.
This triggers a PendingDeprecationWarning in py3.5 -- you're supposed to just write "return" instead (which on earlier versions is equivalent). See PEP 479: https://www.python.org/dev/peps/pep-0479/
I'm not sure exactly when GzipFile.seek started supporting the whence= argument by default -- sometime around python 2.5 from the looks of http://bugs.python.org/issue1355023. But in any case it was definitely there by 2.6, which is now the earliest version we support, so there's no longer any need to monkeypatch it in. This also fixes an error in python 3.5b2, which I haven't bothered to track down further because these are the wages of monkeypatching.