summaryrefslogtreecommitdiffstats
path: root/Python/getargs.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix regression in error message introduced in bpo-29951. (#2028)Serhiy Storchaka2017-06-091-2/+2
| | | | | | | | * Fix regression in error message introduced in bpo-29951. * Add test. * Make the test more strong.
* bpo-30534: Fixed error messages when pass keyword arguments (#1901)Serhiy Storchaka2017-06-061-16/+32
| | | | | | | to functions implemented in C that don't support this. Also unified error messages for functions that don't take positional or keyword arguments.
* bpo-29951: Include function name for some error messages in ↵Michael Seifert2017-04-091-22/+42
| | | | | | | `PyArg_ParseTuple*` (#916) Also changed format specifier for function name from "%s" to "%.200s" and exception messages should start with lowercase letter.
* Issue #29460: _PyArg_NoKeywords(), _PyArg_NoStackKeywords() andSerhiy Storchaka2017-02-061-0/+4
| | | | _PyArg_NoPositional() now are macros.
* Issue #29286: Rename private PyArg_UnpackStack_impl() to unpack_stack()Victor Stinner2017-02-011-12/+12
| | | | Rename also "l" argument to "nargs".
* Issue #29029: Speed up processing positional arguments inSerhiy Storchaka2017-01-171-101/+89
| | | | PyArg_ParseTupleAndKeywords(), _PyArg_ParseTupleAndKeywordsFast() and like.
* Add _PyArg_UnpackStack() function helperVictor Stinner2017-01-171-18/+55
| | | | Issue #29286.
* Add _PyArg_NoStackKeywords() helper functionVictor Stinner2017-01-171-4/+21
| | | | | Issue #29286. Similar to _PyArg_NoKeywords(), but expects a tuple of keyword names, instead of a dict.
* Add _PyArg_ParseStack() helper functionVictor Stinner2017-01-171-21/+69
| | | | | Issue #29286. Function similar to PyArg_ParseTuple(), but uses a C array of PyObject* to pass arguments. Don't support the compatibility mode.
* Rename _PyArg_ParseStack to _PyArg_ParseStackAndKeywordsVictor Stinner2017-01-171-3/+3
| | | | Issue #29286.
* Rename keywords to kwargs in getargs.cVictor Stinner2017-01-161-31/+31
| | | | Issue #29029. Patch written by Serhiy Storchaka.
* Cleanup getargs.cVictor Stinner2017-01-161-49/+17
| | | | | | | Factorize argument checks in: * vgetargskeywordsfast() * vgetargskeywordsfast_impl()
* Issue #28959: Added private macro PyDict_GET_SIZE for retrieving the size of ↵Serhiy Storchaka2016-12-161-3/+3
| | | | dict.
* Issue #19569: Compiler warnings are now emitted if use most of deprecatedSerhiy Storchaka2016-11-201-4/+9
| | | | functions.
* Added the const qualifier to char* variables that refer to readonly internalSerhiy Storchaka2016-11-201-7/+7
| | | | UTF-8 represenatation of Unicode objects.
* Issue #28701: Replace PyUnicode_CompareWithASCIIString with ↵Serhiy Storchaka2016-11-161-1/+1
|\ | | | | | | | | | | _PyUnicode_EqualToASCIIString. The latter function is more readable, faster and doesn't raise exceptions.
| * Issue #28701: Replace PyUnicode_CompareWithASCIIString with ↵Serhiy Storchaka2016-11-161-1/+1
| | | | | | | | | | | | _PyUnicode_EqualToASCIIString. The latter function is more readable, faster and doesn't raise exceptions.
* | va_end() all va_copy()ed va_lists.Christian Heimes2016-09-211-2/+12
| |
* | replace usage of Py_VA_COPY with the (C99) standard va_copyBenjamin Peterson2016-09-211-6/+6
| |
* | Backed out changeset 3934e070c9dbBenjamin Peterson2016-09-111-2/+1
| |
* | Issue #27810: Fix getargs.c compilation on WindowsVictor Stinner2016-09-101-1/+2
| |
* | fix export of size_t parse stack functionBenjamin Peterson2016-09-101-0/+2
| |
* | Emit METH_FASTCALL code in Argument ClinicVictor Stinner2016-09-101-27/+157
| | | | | | | | | | | | | | | | | | Issue #27810: * Modify vgetargskeywordsfast() to work on a C array of PyObject* rather than working on a tuple directly. * Add _PyArg_ParseStack() * Argument Clinic now emits code using the new METH_FASTCALL calling convention
* | Add METH_FASTCALL calling conventionVictor Stinner2016-09-101-1/+2
| | | | | | | | | | | | | | | | | | | | | | Issue #27810: Add a new calling convention for C functions: PyObject* func(PyObject *self, PyObject **args, Py_ssize_t nargs, PyObject *kwnames); Where args is a C array of positional arguments followed by values of keyword arguments. nargs is the number of positional arguments, kwnames are keys of keyword arguments. kwnames can be NULL.
* | replace PY_LONG_LONG with long longBenjamin Peterson2016-09-061-8/+8
| |
* | require a long long data type (closes #27961)Benjamin Peterson2016-09-061-4/+0
| |
* | Issue #27574: Decreased an overhead of parsing keyword arguments in functionsSerhiy Storchaka2016-08-141-12/+437
| | | | | | | | implemented with using Argument Clinic.
* | Issue #26282: PyArg_ParseTupleAndKeywords() and Argument Clinic now supportSerhiy Storchaka2016-06-091-42/+79
| | | | | | | | positional-only and keyword parameters in the same function.
* | Issue #26057: Got rid of nonneeded use of PyUnicode_FromObject().Serhiy Storchaka2016-04-131-18/+8
| |
* | Minor code cleanup for PyArg_UnpackTuple.Raymond Hettinger2016-03-261-9/+8
| |
* | Issue #26312: SystemError is now raised in all programming bugs with usingSerhiy Storchaka2016-02-111-6/+6
| | | | | | | | | | PyArg_ParseTupleAndKeywords(). RuntimeError did raised before in some programming bugs.
* | Issue #26198: ValueError is now raised instead of TypeError on bufferSerhiy Storchaka2016-02-071-2/+7
| | | | | | | | | | overflow in parsing "es#" and "et#" format units. SystemError is now raised instead of TypeError on programmical error in parsing format string.
* | Issue #26198: Fixed error messages for some argument parsing errors.Serhiy Storchaka2016-02-071-12/+20
|\ \ | |/
| * Issue #26198: Fixed error messages for some argument parsing errors.Serhiy Storchaka2016-02-071-12/+20
| | | | | | | | | | Fixed the documented about buffer overflow error for "es#" and "et#" format units.
* | Issue #25923: Added more const qualifiers to signatures of static and ↵Serhiy Storchaka2015-12-251-29/+29
|/ | | | private functions.
* Fixed error message for the "u#" format code.Serhiy Storchaka2015-04-191-3/+4
|\
| * Fixed error message for the "u#" format code.Serhiy Storchaka2015-04-191-3/+4
| |
* | Issue #22581: Use more "bytes-like object" throughout the docs and comments.Serhiy Storchaka2014-12-051-7/+7
|\ \ | |/
| * Issue #22581: Use more "bytes-like object" throughout the docs and comments.Serhiy Storchaka2014-12-051-7/+7
| |
* | #16518: Bring error messages in harmony with docs ("bytes-like object")R David Murray2014-10-051-3/+4
| | | | | | | | | | | | | | | | | | | | Some time ago we changed the docs to consistently use the term 'bytes-like object' in all the contexts where bytes, bytearray, memoryview, etc are used. This patch (by Ezio Melotti) completes that work by changing the error messages that previously reported that certain types did "not support the buffer interface" to instead say that a bytes-like object is required. (The glossary entry for bytes-like object references the discussion of the buffer protocol in the docs.)
* | Issue #22215: Now ValueError is raised instead of TypeError when str or bytesSerhiy Storchaka2014-09-061-13/+12
| | | | | | | | argument contains not permitted null character or byte.
* | Issue #22156: Fix "comparison between signed and unsigned integers" compilerVictor Stinner2014-08-151-2/+2
|/ | | | warnings in the Python/ subdirectory.
* remove dynamic initializer lists for c89 compliance (closes #20595)Benjamin Peterson2014-02-111-3/+11
|
* Issue #20294: Argument Clinic now supports argument parsing for __new__ andLarry Hastings2014-01-191-1/+20
| | | | __init__ functions.
* PY_FORMAT_SIZE_T should not be used with PyErr_Format(), PyErr_Format("%zd") isVictor Stinner2013-11-181-2/+1
| | | | portable
* Use Py_ssize_t type for sizes in getargs.cVictor Stinner2013-11-181-7/+18
| | | | Fix compiler warnings on Windows 64-bit
* remove an outdated commentVictor Stinner2013-11-061-1/+0
| | | | The comment is meaningless since changeset 4e985a96a612.
* Re #18521: move array bounds check before array access.Georg Brandl2013-10-141-1/+1
|
* Issue #9566: Fix compilater warnings on Windows 64-bitVictor Stinner2013-06-041-1/+1
|
* Use PY_FORMAT_SIZE_T because Visual Studio does not understand %zd format.Richard Oudkerk2013-05-181-1/+1
|