summaryrefslogtreecommitdiffstats
path: root/Modules
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Issue #28768: Fix implicit declaration of function _setmode. Patch by ↵Steve Dower2016-12-282-0/+6
|\ \ \ | |/ / | | | | | | Masayuki Yamamoto
| * | Issue #28768: Fix implicit declaration of function _setmode. Patch by ↵Steve Dower2016-12-282-0/+6
| | | | | | | | | | | | Masayuki Yamamoto
* | | Issue #28427: old keys should not remove new values fromAntoine Pitrou2016-12-272-1/+72
|\ \ \ | |/ / | | | | | | WeakValueDictionary when collecting from another thread.
| * | Issue #28427: old keys should not remove new values fromAntoine Pitrou2016-12-272-1/+72
| |\ \ | | |/ | | | | | | WeakValueDictionary when collecting from another thread.
| | * Issue #28427: old keys should not remove new values fromAntoine Pitrou2016-12-272-1/+71
| | | | | | | | | | | | WeakValueDictionary when collecting from another thread.
* | | Issue #29004: Merge crc_hqx() doc from 3.6Martin Panter2016-12-242-4/+4
|\ \ \ | |/ /
| * | Issue #29004: Merge crc_hqx() doc from 3.5Martin Panter2016-12-242-4/+4
| |\ \ | | |/
| | * Issue #29004: Document binascii.crc_hqx() implements CRC-CCITTMartin Panter2016-12-242-4/+4
| | |
* | | Merge from 3.6.Serhiy Storchaka2016-12-211-0/+2
|\ \ \ | |/ /
| * | Merge from 3.5.Serhiy Storchaka2016-12-211-0/+2
| |\ \ | | |/
| | * Issue #28871: Fixed a crash when deallocate deep ElementTree.Serhiy Storchaka2016-12-211-0/+2
| | |
| | * Issue #28147: Fix a memory leak in split-table dictionariesINADA Naoki2016-12-201-0/+10
| | | | | | | | | | | | setattr() must not convert combined table into split table.
* | | Issue #28822: Adjust indices handling of PyUnicode_FindChar().Xiang Zhang2016-12-201-0/+22
| | |
* | | Issue #20191: Fixed a crash in resource.prlimit() when pass a sequence thatSerhiy Storchaka2016-12-191-33/+31
|\ \ \ | |/ / | | | | | | doesn't own its elements as limits.
| * | Issue #20191: Fixed a crash in resource.prlimit() when pass a sequence thatSerhiy Storchaka2016-12-191-33/+31
| |\ \ | | |/ | | | | | | doesn't own its elements as limits.
| | * Issue #20191: Fixed a crash in resource.prlimit() when pass a sequence thatSerhiy Storchaka2016-12-191-33/+31
| | | | | | | | | | | | doesn't own its elements as limits.
* | | Issue #28959: Added private macro PyDict_GET_SIZE for retrieving the size of ↵Serhiy Storchaka2016-12-1611-35/+23
| | | | | | | | | | | | dict.
* | | Merge 3.6Victor Stinner2016-12-151-0/+14
|\ \ \ | |/ /
| * | Fix a memory leak in split-table dictionariesVictor Stinner2016-12-151-0/+14
| | | | | | | | | | | | | | | | | | | | | Issue #28147: Fix a memory leak in split-table dictionaries: setattr() must not convert combined table into split table. Patch written by INADA Naoki.
| * | _asyncio uses _PyObject_CallMethodIdObjArgs()Victor Stinner2016-12-151-9/+10
| | | | | | | | | | | | | | | | | | | | | | | | Issue #28920: Replace _PyObject_CallMethodId(obj, meth, "O", arg) with _PyObject_CallMethodIdObjArgs(obj, meth, arg, NULL) to avoid _PyObject_CallMethodId() special case when arg is a tuple. If arg is a tuple, _PyObject_CallMethodId() unpacks the tuple: obj.meth(*arg).
* | | Fixes maximum usable length of buffer for formatting time zone in localtime().Steve Dower2016-12-141-1/+1
|\ \ \ | |/ /
| * | Fixes maximum usable length of buffer for formatting time zone in localtime().Steve Dower2016-12-141-1/+1
| | |
* | | Initialize variables to fix compiler warningsVictor Stinner2016-12-092-4/+4
| | | | | | | | | | | | | | | Warnings seen on the "AMD64 Debian PGO 3.x" buildbot. Warnings are false positive, but variable initialization should not harm performances.
* | | Use PyObject_CallFunctionObjArgs()Victor Stinner2016-12-091-8/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace PyObject_CallFunction() with PyObject_CallFunctionObjArgs() when the format string was only made of "O" formats, PyObject* arguments. PyObject_CallFunctionObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Use _PyObject_CallMethodIdObjArgs()Victor Stinner2016-12-093-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() in various modules when the format string was only made of "O" formats, PyObject* arguments. _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Use _PyObject_CallMethodIdObjArgs() in _ioVictor Stinner2016-12-095-10/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() when the format string was only made of "O" formats, PyObject* arguments. _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Use _PyObject_CallMethodIdObjArgs() in _datetimeVictor Stinner2016-12-091-8/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() when the format string was only made of "O" formats, PyObject* arguments. _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Use _PyObject_CallMethodIdObjArgs() in _elementtreeVictor Stinner2016-12-091-9/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() when the format string was only made of "O" formats, PyObject* arguments. _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Use _PyObject_CallMethodIdObjArgs() in _ctypesVictor Stinner2016-12-091-13/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() in unpickle(). _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string. Replace _PyObject_CallMethodId() with _PyObject_GetAttrId()+PyObject_Call() for the second call since it requires to "unpack" a tuple. Add also a check in the type of the second parameter (state): it must be a tuple.
* | | Fix refleak introduced in change 032cbdb596feVictor Stinner2016-12-091-0/+1
| | | | | | | | | | | | Issue #28915.
* | | Use _PyObject_CallMethodIdObjArgs() in _asyncioVictor Stinner2016-12-091-17/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() when the format string was only made of "O" formats, PyObject* arguments. _PyObject_CallMethodIdObjArgs() avoids the creation of a temporary tuple and doesn't have to parse a format string.
* | | Issue #28915: Use _PyObject_CallNoArg()Victor Stinner2016-12-092-3/+3
| | | | | | | | | | | | Replace PyObject_CallFunction(func, NULL) with _PyObject_CallNoArg(func).
* | | time_strptime() uses PyObject_Call()Victor Stinner2016-12-081-7/+13
| | | | | | | | | | | | | | | | | | Issue #28915: Use PyObject_Call() to pass a tuple of positional arguments, instead of relying on _PyObject_CallMethodId() weird behaviour to unpack the tuple.
* | | build_struct_time() uses Py_BuildValue()Victor Stinner2016-12-081-11/+20
| | | | | | | | | | | | | | | | | | Issue #28915: Avoid calling _PyObject_CallMethodId() with "(...)" format to avoid the creation of a temporary tuple: use Py_BuildValue() with _PyObject_CallMethodIdObjArgs().
* | | Use _PyObject_CallMethodIdObjArgs()Victor Stinner2016-12-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Issue #28915: Replace _PyObject_CallMethodId() with _PyObject_CallMethodIdObjArgs() when the format string only use the format 'O' for objects, like "(O)". _PyObject_CallMethodIdObjArgs() avoids the code to parse a format string and avoids the creation of a temporary tuple.
* | | Don't parenthesis in _PyObject_CallMethodId() formatVictor Stinner2016-12-083-3/+3
| | | | | | | | | | | | | | | Issue #28915: Without parenthesis, _PyObject_CallMethodId() avoids the creation a temporary tuple, and so is more efficient.
* | | Merge from 3.6.Serhiy Storchaka2016-12-071-1/+1
|\ \ \ | |/ /
| * | Merge from 3.5.Serhiy Storchaka2016-12-071-1/+1
| |\ \ | | |/
| | * Change order of io.UnsupportedOperation base classes.Serhiy Storchaka2016-12-071-1/+1
| | | | | | | | | | | | This makes tests passing after changes by issue #5322.
| * | Issue #28843: Fix asyncio C Task to handle exceptions __traceback__.Yury Selivanov2016-12-011-0/+5
| | |
| * | Add TCP_CONGESTION and TCP_USER_TIMEOUTVictor Stinner2016-11-291-0/+6
| | | | | | | | | | | | | | | | | | | | | Issue #26273: Add new socket.TCP_CONGESTION (Linux 2.6.13) and socket.TCP_USER_TIMEOUT (Linux 2.6.37) constants. Patch written by Omar Sandoval.
* | | Use _PyObject_CallNoArg()Victor Stinner2016-12-066-9/+9
| | | | | | | | | | | | | | | | | | | | | Replace: PyObject_CallFunctionObjArgs(callable, NULL) with: _PyObject_CallNoArg(callable)
* | | Use _PyObject_CallNoArg()Victor Stinner2016-12-067-22/+22
| | | | | | | | | | | | | | | | | | | | | Replace: PyObject_CallObject(callable, NULL) with: _PyObject_CallNoArg(callable)
* | | Issue #28152: Fix -Wunreachable-code warning on clangVictor Stinner2016-12-051-2/+5
| | | | | | | | | | | | | | | Replace 0 with (0) to ignore a compiler warning about dead code on "((int)(SEM_VALUE_MAX) < 0)": SEM_VALUE_MAX is not negative on Linux.
* | | Issue #28152: Fix -Wunreachable-code warning on clangVictor Stinner2016-12-051-5/+5
| | | | | | | | | | | | | | | Replace C if() with precompiler #if to fix a warning on dead code when using clang.
* | | Issue #28152: Fix -Wunreachable-code warnings on ClangVictor Stinner2016-12-052-0/+14
| | | | | | | | | | | | Don't declare dead code when the code is declared with Clang.
* | | Issue #28858: Remove _PyObject_CallArg1() macroVictor Stinner2016-12-056-12/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace _PyObject_CallArg1(func, arg) with PyObject_CallFunctionObjArgs(func, arg, NULL) Using the _PyObject_CallArg1() macro increases the usage of the C stack, which was unexpected and unwanted. PyObject_CallFunctionObjArgs() doesn't have this issue.
* | | Backed out changeset b9c9691c72c5Victor Stinner2016-12-0411-31/+33
| | | | | | | | | | | | | | | | | | Issue #28858: The change b9c9691c72c5 introduced a regression. It seems like _PyObject_CallArg1() uses more stack memory than PyObject_CallFunctionObjArgs().
* | | Merge 3.6 (issue #28843)Yury Selivanov2016-12-011-0/+5
| | |
* | | Replace PyObject_CallFunction() with fastcallVictor Stinner2016-12-014-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace PyObject_CallFunction(func, "O", arg) and PyObject_CallFunction(func, "O", arg, NULL) with _PyObject_CallArg1(func, arg) Replace PyObject_CallFunction(func, NULL) with _PyObject_CallNoArg(func) _PyObject_CallNoArg() and _PyObject_CallArg1() are simpler and don't allocate memory on the C stack.
generated by cgit v0.12 at 2025-12-12 05:15:29 (GMT)