diff -r 9d0f4da4d531 Include/pyfpe.h --- a/Include/pyfpe.h Sat Sep 17 01:30:48 2016 +0300 +++ b/Include/pyfpe.h Fri Sep 16 21:38:27 2016 -0300 @@ -45,10 +45,10 @@ * Define macros for handling SIGFPE. * Lee Busby, LLNL, November, 1996 * busby1@llnl.gov - * + * ********************************************* * Overview of the system for handling SIGFPE: - * + * * This file (Include/pyfpe.h) defines a couple of "wrapper" macros for * insertion into your Python C code of choice. Their proper use is * discussed below. The file Python/pyfpe.c defines a pair of global @@ -59,33 +59,33 @@ * named fpectl. This module is standard in every respect. It can be loaded * either statically or dynamically as you choose, and like any other * Python module, has no effect until you import it. - * + * * In the general case, there are three steps toward handling SIGFPE in any * Python code: - * + * * 1) Add the *_PROTECT macros to your C code as required to protect * dangerous floating point sections. - * + * * 2) Turn on the inclusion of the code by adding the ``--with-fpectl'' * flag at the time you run configure. If the fpectl or other modules * which use the *_PROTECT macros are to be dynamically loaded, be * sure they are compiled with WANT_SIGFPE_HANDLER defined. - * + * * 3) When python is built and running, import fpectl, and execute * fpectl.turnon_sigfpe(). This sets up the signal handler and enables * generation of SIGFPE whenever an exception occurs. From this point * on, any properly trapped SIGFPE should result in the Python * FloatingPointError exception. - * + * * Step 1 has been done already for the Python kernel code, and should be * done soon for the NumPy array package. Step 2 is usually done once at * python install time. Python's behavior with respect to SIGFPE is not * changed unless you also do step 3. Thus you can control this new * facility at compile time, or run time, or both. - * - ******************************** + * + ******************************** * Using the macros in your code: - * + * * static PyObject *foobar(PyObject *self,PyObject *args) * { * .... @@ -94,17 +94,17 @@ * PyFPE_END_PROTECT(result) * .... * } - * + * * If a floating point error occurs in dangerous_op, foobar returns 0 (NULL), * after setting the associated value of the FloatingPointError exception to * "Error in foobar". ``Dangerous_op'' can be a single operation, or a block * of code, function calls, or any combination, so long as no alternate * return is possible before the PyFPE_END_PROTECT macro is reached. - * + * * The macros can only be used in a function context where an error return * can be recognized as signaling a Python exception. (Generally, most * functions that return a PyObject * will qualify.) - * + * * Guido's original design suggestion for PyFPE_START_PROTECT and * PyFPE_END_PROTECT had them open and close a local block, with a locally * defined jmp_buf and jmp_buf pointer. This would allow recursive nesting @@ -112,17 +112,17 @@ * variables need to be declared with the "volatile" type qualifier to keep * setjmp from corrupting their values. Some current implementations seem * to be more restrictive. For example, the HPUX man page for setjmp says - * + * * Upon the return from a setjmp() call caused by a longjmp(), the * values of any non-static local variables belonging to the routine * from which setjmp() was called are undefined. Code which depends on * such values is not guaranteed to be portable. - * + * * I therefore decided on a more limited form of nesting, using a counter * variable (PyFPE_counter) to keep track of any recursion. If an exception * occurs in an ``inner'' pair of macros, the return will apparently * come from the outermost level. - * + * */ #ifdef WANT_SIGFPE_HANDLER @@ -146,14 +146,14 @@ * this statement so that it gets executed *before* the unsafe expression * which we're trying to protect. That pretty well messes things up, * of course. - * + * * If the expression(s) you're trying to protect don't happen to return a * value, you will need to manufacture a dummy result just to preserve the * correct ordering of statements. Note that the macro passes the address * of its argument (so you need to give it something which is addressable). * If your expression returns multiple results, pass the last such result * to PyFPE_END_PROTECT. - * + * * Note that PyFPE_dummy returns a double, which is cast to int. * This seeming insanity is to tickle the Floating Point Unit (FPU). * If an exception has occurred in a preceding floating point operation, diff -r 9d0f4da4d531 Include/pyport.h --- a/Include/pyport.h Sat Sep 17 01:30:48 2016 +0300 +++ b/Include/pyport.h Fri Sep 16 21:38:27 2016 -0300 @@ -748,7 +748,7 @@ #define PY_LITTLE_ENDIAN 1 #endif -#ifdef Py_BUILD_CORE +#ifdef Py_BUILD_CORE /* * Macros to protect CRT calls against instant termination when passed an * invalid parameter (issue23524). diff -r 9d0f4da4d531 Misc/coverity_model.c --- a/Misc/coverity_model.c Sat Sep 17 01:30:48 2016 +0300 +++ b/Misc/coverity_model.c Fri Sep 16 21:38:27 2016 -0300 @@ -139,7 +139,7 @@ build_struct_time(int y, int m, int d, int hh, int mm, int ss, int dstflag) { PyObject *result; - + __coverity_tainted_data_sanitize__(y); __coverity_tainted_data_sanitize__(m); __coverity_tainted_data_sanitize__(d); diff -r 9d0f4da4d531 Modules/_io/winconsoleio.c --- a/Modules/_io/winconsoleio.c Sat Sep 17 01:30:48 2016 +0300 +++ b/Modules/_io/winconsoleio.c Fri Sep 16 21:38:27 2016 -0300 @@ -43,7 +43,7 @@ if (handle == INVALID_HANDLE_VALUE) return '\0'; - + if (!GetConsoleMode(handle, &mode)) return '\0'; @@ -786,7 +786,7 @@ bytes_size = WideCharToMultiByte(CP_UTF8, 0, buf, len, NULL, 0, NULL, NULL); Py_END_ALLOW_THREADS - + if (!bytes_size) { DWORD err = GetLastError(); PyMem_Free(buf); @@ -837,7 +837,7 @@ { PyObject *bytes; Py_ssize_t bytes_size; - + if (self->handle == INVALID_HANDLE_VALUE) return err_closed(); if (!self->readable) @@ -912,7 +912,7 @@ wlen = MultiByteToWideChar(CP_UTF8, 0, b->buf, len, NULL, 0); } Py_END_ALLOW_THREADS - + if (!wlen) return PyErr_SetFromWindowsErr(0); @@ -939,7 +939,7 @@ } else res = 0; Py_END_ALLOW_THREADS - + if (!res) { DWORD err = GetLastError(); PyMem_Free(wbuf); @@ -979,7 +979,7 @@ { if (self->handle == INVALID_HANDLE_VALUE) return err_closed(); - + Py_RETURN_TRUE; } diff -r 9d0f4da4d531 Modules/_struct.c --- a/Modules/_struct.c Sat Sep 17 01:30:48 2016 +0300 +++ b/Modules/_struct.c Fri Sep 16 21:38:27 2016 -0300 @@ -486,7 +486,7 @@ return unpack_halffloat(p, 1); #else return unpack_halffloat(p, 0); -#endif +#endif } static PyObject * diff -r 9d0f4da4d531 Modules/expat/expat.h --- a/Modules/expat/expat.h Sat Sep 17 01:30:48 2016 +0300 +++ b/Modules/expat/expat.h Fri Sep 16 21:38:27 2016 -0300 @@ -788,20 +788,20 @@ (resumable = 0) an already suspended parser. Some call-backs may still follow because they would otherwise get lost. Examples: - endElementHandler() for empty elements when stopped in - startElementHandler(), - - endNameSpaceDeclHandler() when stopped in endElementHandler(), + startElementHandler(), + - endNameSpaceDeclHandler() when stopped in endElementHandler(), and possibly others. Can be called from most handlers, including DTD related call-backs, except when parsing an external parameter entity and resumable != 0. Returns XML_STATUS_OK when successful, XML_STATUS_ERROR otherwise. - Possible error codes: + Possible error codes: - XML_ERROR_SUSPENDED: when suspending an already suspended parser. - XML_ERROR_FINISHED: when the parser has already finished. - XML_ERROR_SUSPEND_PE: when suspending while parsing an external PE. - When resumable != 0 (true) then parsing is suspended, that is, - XML_Parse() and XML_ParseBuffer() return XML_STATUS_SUSPENDED. + When resumable != 0 (true) then parsing is suspended, that is, + XML_Parse() and XML_ParseBuffer() return XML_STATUS_SUSPENDED. Otherwise, parsing is aborted, that is, XML_Parse() and XML_ParseBuffer() return XML_STATUS_ERROR with error code XML_ERROR_ABORTED. @@ -812,7 +812,7 @@ the externalEntityRefHandler() to call XML_StopParser() on the parent parser (recursively), if one wants to stop parsing altogether. - When suspended, parsing can be resumed by calling XML_ResumeParser(). + When suspended, parsing can be resumed by calling XML_ResumeParser(). */ XMLPARSEAPI(enum XML_Status) XML_StopParser(XML_Parser parser, XML_Bool resumable); @@ -820,7 +820,7 @@ /* Resumes parsing after it has been suspended with XML_StopParser(). Must not be called from within a handler call-back. Returns same status codes as XML_Parse() or XML_ParseBuffer(). - Additional error code XML_ERROR_NOT_SUSPENDED possible. + Additional error code XML_ERROR_NOT_SUSPENDED possible. *Note*: This must be called on the most deeply nested child parser instance @@ -932,7 +932,7 @@ be within the relevant markup. When called outside of the callback functions, the position indicated will be just past the last parse event (regardless of whether there was an associated callback). - + They may also be called after returning from a call to XML_Parse or XML_ParseBuffer. If the return value is XML_STATUS_ERROR then the location is the location of the character at which the error diff -r 9d0f4da4d531 Modules/expat/expat_external.h --- a/Modules/expat/expat_external.h Sat Sep 17 01:30:48 2016 +0300 +++ b/Modules/expat/expat_external.h Fri Sep 16 21:38:27 2016 -0300 @@ -101,7 +101,7 @@ #ifdef XML_LARGE_SIZE /* Use large integers for file/stream positions. */ #if defined(XML_USE_MSC_EXTENSIONS) && _MSC_VER < 1400 -typedef __int64 XML_Index; +typedef __int64 XML_Index; typedef unsigned __int64 XML_Size; #else typedef long long XML_Index; diff -r 9d0f4da4d531 Modules/expat/pyexpatns.h --- a/Modules/expat/pyexpatns.h Sat Sep 17 01:30:48 2016 +0300 +++ b/Modules/expat/pyexpatns.h Fri Sep 16 21:38:27 2016 -0300 @@ -26,7 +26,7 @@ * http://lxr.mozilla.org/seamonkey/source/modules/libimg/png/mozpngconf.h#115 * * The list of relevant exported symbols can be had with this command: - * + * nm pyexpat.so \ | grep -v " [a-zBUA] " \ | grep -v "_fini\|_init\|initpyexpat" diff -r 9d0f4da4d531 PC/getpathp.c --- a/PC/getpathp.c Sat Sep 17 01:30:48 2016 +0300 +++ b/PC/getpathp.c Fri Sep 16 21:38:27 2016 -0300 @@ -540,7 +540,7 @@ if (buf[0]) wcscat_s(buf, bufsiz, L";"); wchar_t *b = &buf[wcslen(buf)]; - + wcscat_s(buf, bufsiz, prefix); join(b, wline); diff -r 9d0f4da4d531 Parser/myreadline.c --- a/Parser/myreadline.c Sat Sep 17 01:30:48 2016 +0300 +++ b/Parser/myreadline.c Fri Sep 16 21:38:27 2016 -0300 @@ -172,7 +172,7 @@ buf = PyMem_RawMalloc(u8len + 1); u8len = WideCharToMultiByte(CP_UTF8, 0, wbuf, total_read, buf, u8len, NULL, NULL); buf[u8len] = '\0'; - + exit: if (wbuf != wbuf_local) PyMem_RawFree(wbuf); @@ -204,11 +204,11 @@ #ifdef MS_WINDOWS if (!Py_LegacyWindowsStdioFlag && sys_stdin == stdin) { HANDLE hStdIn; - + _Py_BEGIN_SUPPRESS_IPH hStdIn = (HANDLE)_get_osfhandle(fileno(sys_stdin)); _Py_END_SUPPRESS_IPH - + if (_get_console_type(hStdIn) == 'r') { fflush(sys_stdout); if (prompt)