Rooba
/
cpython
mirror of https://github.com/python/cpython.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cpython/Include/modsupport.h

156 lines
5.9 KiB
C
Raw Normal View History

Added copyright notice.
1991-02-19 12:39:46 +00:00
ANSI-fication of the sources -- remove Py_PROTO!
2000-07-08 17:25:55 +00:00
#ifndef Py_MODSUPPORT_H
#define Py_MODSUPPORT_H
#ifdef __cplusplus
extern "C" {
#endif
Initial revision
1990-10-14 12:07:46 +00:00
/* Module support interface */
* Changed many files to use mkvalue() instead of newtupleobject(). * Fixcprt.py: added [-y file] option, do only files younger than file. * modsupport.[ch]: added vmkvalue(). * intobject.c: use mkvalue(). * stringobject.c: added "formatstring"; renamed string* to string_*; ceval.c: call formatstring for string % value. * longobject.c: close memory leak in divmod. * parsetok.c: set result node to NULL when returning an error.
1993-03-16 12:15:04 +00:00
#include <stdarg.h>
Merge alpha100 branch back to main trunk
1994-08-01 11:34:53 +00:00
Merge ssize_t branch.
2006-02-15 17:27:45 +00:00
/* If PY_SSIZE_T_CLEAN is defined, each functions treats #-specifier
to mean Py_ssize_t */
#ifdef PY_SSIZE_T_CLEAN
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
#define PyArg_Parse _PyArg_Parse_SizeT
#define PyArg_ParseTuple _PyArg_ParseTuple_SizeT
#define PyArg_ParseTupleAndKeywords _PyArg_ParseTupleAndKeywords_SizeT
#define PyArg_VaParse _PyArg_VaParse_SizeT
#define PyArg_VaParseTupleAndKeywords _PyArg_VaParseTupleAndKeywords_SizeT
#define Py_BuildValue _Py_BuildValue_SizeT
#define Py_VaBuildValue _Py_VaBuildValue_SizeT
Merge p3yk branch with the trunk up to revision 45595. This breaks a fair number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
2006-04-21 10:40:58 +00:00
#else
PyAPI_FUNC(PyObject *) _Py_VaBuildValue_SizeT(const char *, va_list);
Merge ssize_t branch.
2006-02-15 17:27:45 +00:00
#endif
Issue #11626: Add _SizeT functions to stable ABI.
2012-06-23 22:00:30 +00:00
/* Due to a glitch in 3.2, the _SizeT versions weren't exported from the DLL. */
#if !defined(PY_SSIZE_T_CLEAN) || !defined(Py_LIMITED_API) || Py_LIMITED_API+0 >= 0x03030000
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(int) PyArg_Parse(PyObject *, const char *, ...);
remove support GCC PyArg_ParseTuple format patch, last seen in 2006
2013-05-13 04:08:28 +00:00
PyAPI_FUNC(int) PyArg_ParseTuple(PyObject *, const char *, ...);
Excise DL_EXPORT from Include. Thanks to Skip Montanaro and Kalle Svensson for the patches.
2002-08-12 07:21:58 +00:00
PyAPI_FUNC(int) PyArg_ParseTupleAndKeywords(PyObject *, PyObject *,
Revert backwards-incompatible const changes.
2006-02-27 16:46:16 +00:00
const char *, char **, ...);
prevent the dict constructor from accepting non-string keyword args #8419 This adds PyArg_ValidateKeywordArguments, which checks that keyword arguments are all strings, using an optimized method if possible.
2010-04-24 18:21:17 +00:00
PyAPI_FUNC(int) PyArg_ValidateKeywordArguments(PyObject *);
Use Py_ssize_t for PyArg_UnpackTuple arguments.
2006-03-01 04:06:10 +00:00
PyAPI_FUNC(int) PyArg_UnpackTuple(PyObject *, const char *, Py_ssize_t, Py_ssize_t, ...);
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(PyObject *) Py_BuildValue(const char *, ...);
Merge p3yk branch with the trunk up to revision 45595. This breaks a fair number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
2006-04-21 10:40:58 +00:00
PyAPI_FUNC(PyObject *) _Py_BuildValue_SizeT(const char *, ...);
Issue #11626: Add _SizeT functions to stable ABI.
2012-06-23 22:00:30 +00:00
#endif
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
#ifndef Py_LIMITED_API
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(int) _PyArg_NoKeywords(const char *funcname, PyObject *kw);
Issue #20294: Argument Clinic now supports argument parsing for __new__ and __init__ functions.
2014-01-19 07:50:21 +00:00
PyAPI_FUNC(int) _PyArg_NoPositional(const char *funcname, PyObject *args);
Merge alpha100 branch back to main trunk
1994-08-01 11:34:53 +00:00
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(int) PyArg_VaParse(PyObject *, const char *, va_list);
Add PyArg_VaParseTupleAndKeywords(). Document this function and PyArg_VaParse(). Closes patch #550732. Thanks Greg Chapman.
2004-07-10 22:20:32 +00:00
PyAPI_FUNC(int) PyArg_VaParseTupleAndKeywords(PyObject *, PyObject *,
Revert backwards-incompatible const changes.
2006-02-27 16:46:16 +00:00
const char *, char **, va_list);
Issue #11626: Add _SizeT functions to stable ABI.
2012-06-23 22:00:30 +00:00
#endif
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(PyObject *) Py_VaBuildValue(const char *, va_list);
New getargs() function. Define macros with conventional names, except get*str*arg --> get*Str*arg; get*str*arg fetches a C string.
1992-01-27 16:50:21 +00:00
Add const to several API functions that take char *. In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
2005-12-10 18:50:16 +00:00
PyAPI_FUNC(int) PyModule_AddObject(PyObject *, const char *, PyObject *);
PyAPI_FUNC(int) PyModule_AddIntConstant(PyObject *, const char *, long);
PyAPI_FUNC(int) PyModule_AddStringConstant(PyObject *, const char *, const char *);
Merged revisions 60176-60209 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r60178 | georg.brandl | 2008-01-21 22:05:49 +0100 (Mon, 21 Jan 2008) | 2 lines #1715: include sub-extension modules in pydoc text output. ........ r60179 | georg.brandl | 2008-01-21 22:14:21 +0100 (Mon, 21 Jan 2008) | 2 lines Add a "const" to make gcc happy. ........ r60180 | georg.brandl | 2008-01-21 22:19:07 +0100 (Mon, 21 Jan 2008) | 2 lines Add the correct build dir when building with pydebug. ........ r60181 | georg.brandl | 2008-01-21 22:23:15 +0100 (Mon, 21 Jan 2008) | 3 lines Patch #1720595: add T_BOOL to the range of structmember types. Patch by Angelo Mottola, reviewed by MvL, tests by me. ........ r60182 | georg.brandl | 2008-01-21 22:28:32 +0100 (Mon, 21 Jan 2008) | 2 lines Reformat some ugly code. ........ r60187 | brett.cannon | 2008-01-22 00:50:16 +0100 (Tue, 22 Jan 2008) | 4 lines Make's MAKEFLAGS variable is set to a string containing the single-letter arguments to Make. This means there are no hyphens. Fix the '-s' check to silence distutils to now work. ........ r60188 | gregory.p.smith | 2008-01-22 01:19:41 +0100 (Tue, 22 Jan 2008) | 3 lines accepts and closes issue #1221598: adds an optional callback to ftplib.FTP storbinary() and storlines() methods. ........ r60189 | gregory.p.smith | 2008-01-22 02:12:02 +0100 (Tue, 22 Jan 2008) | 2 lines Replace spam.acquire() try: ... finally: spam.release() with "with spam:" ........ r60190 | gregory.p.smith | 2008-01-22 02:20:42 +0100 (Tue, 22 Jan 2008) | 4 lines - Fix Issue #1703448: A joined thread could show up in the threading.enumerate() list after the join() for a brief period until it actually exited. ........ r60193 | georg.brandl | 2008-01-22 08:53:31 +0100 (Tue, 22 Jan 2008) | 2 lines Fix \xhh specs, #1889. ........ r60198 | christian.heimes | 2008-01-22 16:01:25 +0100 (Tue, 22 Jan 2008) | 1 line Fixed a missing (X) in define ........ r60199 | christian.heimes | 2008-01-22 16:25:18 +0100 (Tue, 22 Jan 2008) | 2 lines Don't repeat yourself Added the macros PyModule_AddIntMacro and PyModule_AddStringMacro. They shorten PyModule_AddIntConstant(m, "AF_INET", AF_INET) to PyModule_AddIntMacro(m, AF_INET) ........ r60201 | raymond.hettinger | 2008-01-22 20:51:41 +0100 (Tue, 22 Jan 2008) | 1 line Document when to use izip_longest(). ........ r60202 | georg.brandl | 2008-01-22 20:56:03 +0100 (Tue, 22 Jan 2008) | 2 lines Fix for #1087741 patch. ........ r60203 | raymond.hettinger | 2008-01-22 21:18:53 +0100 (Tue, 22 Jan 2008) | 1 line Give zip() the same guarantee as izip() for left-to-right evaluation. ........ r60204 | raymond.hettinger | 2008-01-22 23:09:26 +0100 (Tue, 22 Jan 2008) | 1 line Improve variable name in sample code ........ r60205 | gregory.p.smith | 2008-01-23 00:15:34 +0100 (Wed, 23 Jan 2008) | 2 lines docstring and comment updates suggested by Giampaolo Rodola' ........ r60207 | raymond.hettinger | 2008-01-23 01:04:40 +0100 (Wed, 23 Jan 2008) | 1 line Let pprint() support sets and frozensets (suggested by David Mertz). ........ r60208 | guido.van.rossum | 2008-01-23 02:18:27 +0100 (Wed, 23 Jan 2008) | 4 lines I'm tired of these tests breaking at Google due to our large number of users and groups in LDAP/NIS. So I'm limiting the extra-heavy part of the tests to passwd/group files with at most 1000 entries. ........
2008-01-23 08:24:23 +00:00
#define PyModule_AddIntMacro(m, c) PyModule_AddIntConstant(m, #c, c)
#define PyModule_AddStringMacro(m, c) PyModule_AddStringConstant(m, #c, c)
Issue 24365: Conditionalize PEP 489 additions to the stable ABI Patch by Petr Viktorin.
2015-06-02 23:06:47 +00:00
#if !defined(Py_LIMITED_API) || Py_LIMITED_API+0 >= 0x03050000
/* New in 3.5 */
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
PyAPI_FUNC(int) PyModule_SetDocString(PyObject *, const char *);
PyAPI_FUNC(int) PyModule_AddFunctions(PyObject *, PyMethodDef *);
PyAPI_FUNC(int) PyModule_ExecDef(PyObject *module, PyModuleDef *def);
Issue 24365: Conditionalize PEP 489 additions to the stable ABI Patch by Petr Viktorin.
2015-06-02 23:06:47 +00:00
#endif
Merge ssize_t branch.
2006-02-15 17:27:45 +00:00
Issue #6012: Add cleanup support to O& argument parsing.
2009-05-29 14:47:46 +00:00
#define Py_CLEANUP_SUPPORTED 0x20000
from __future__ import with_statement addon for 'with', mostly written by Neal.
2006-02-28 19:02:24 +00:00
#define PYTHON_API_VERSION 1013
#define PYTHON_API_STRING "1013"
api version checking
1995-01-09 17:47:20 +00:00
/* The API version is maintained (independently from the Python version)
so we can detect mismatches between the interpreter and dynamically
Spelling fixes supplied by Rob W. W. Hooft. All these are fixes in either comments, docstrings or error messages. I fixed two minor things in test_winreg.py ("didn't" -> "Didn't" and "Didnt" -> "Didn't"). There is a minor style issue involved: Guido seems to have preferred English grammar (behaviour, honour) in a couple places. This patch changes that to American, which is the more prominent style in the source. I prefer English myself, so if English is preferred, I'd be happy to supply a patch myself ;)
2000-07-16 12:04:32 +00:00
loaded modules. These are diagnosed by an error message but
Two bumps for the price of one (PYTHON_API_VERSION)
1996-07-30 16:41:02 +00:00
the module is still loaded (because the mismatch can only be tested
after loading the module). The error message is intended to
explain the core dump a few seconds later.
api version checking
1995-01-09 17:47:20 +00:00
Add PYTHON_API_STRING, which is PYTHON_API_VERSION as a string literal. Under Windows, add MS_DLL_ID and MS_DLL_VERSION_ID for Mark H. Independent change: if Py_TRACE_REFS is defined, rename Py_InitModule4 so so linking with incompatible modules will create a link time error. [Backing out of previous changes (also for modsupport.c) to test the latter at runtime.]
1996-08-22 22:55:47 +00:00
The symbol PYTHON_API_STRING defines the same value as a string
literal. *** PLEASE MAKE SURE THE DEFINITIONS MATCH. ***
api version checking
1995-01-09 17:47:20 +00:00
Please add a line or two to the top of this log for each API
version change:
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
22-Feb-2006 MvL 1013 PEP 353 - long indices for sequence lengths
from __future__ import with_statement addon for 'with', mostly written by Neal.
2006-02-28 19:02:24 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
19-Aug-2002 GvR 1012 Changes to string object struct for
interning changes, saving 3 bytes.
SF patch 576101, by Oren Tirosh: alternative implementation of interning. I modified Oren's patch significantly, but the basic idea and most of the implementation is unchanged. Interned strings created with PyString_InternInPlace() are now mortal, and you must keep a reference to the resulting string around; use the new function PyString_InternImmortal() to create immortal interned strings.
2002-08-19 21:43:18 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
17-Jul-2001 GvR 1011 Descr-branch, just to be on the safe side
Merge of descr-branch back into trunk.
2001-08-02 04:15:00 +00:00
The addition of new parameters to functions in the Python/C API requires that PYTHON_API_VERSION be incremented.
2001-01-25 22:13:34 +00:00
25-Jan-2001 FLD 1010 Parameters added to PyCode_New() and
PyFrame_New(); Python 2.1a2
Version updated to 1.6; API version to 1009.
2000-03-29 01:46:45 +00:00
14-Mar-2000 GvR 1009 Unicode API added
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
3-Jan-1999 GvR 1007 Decided to change back! (Don't reuse 1008!)
New version identification scheme. The version numbers are now exported by Python.h. Also rolled back the API version change -- it's back to 1007!
1999-01-03 12:40:24 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
3-Dec-1998 GvR 1008 Python 1.5.2b1
New API version (enough has changed!).
1998-12-03 18:18:12 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
18-Jan-1997 GvR 1007 string interning and other speedups
Bump API version due to the various speedup hacks.
1997-01-18 07:54:03 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
11-Oct-1996 GvR renamed Py_Ellipses to Py_Ellipsis :-(
Ellipses -> Ellipsis rename (the dictionary really says that it should be Ellipsis!). Bumped the API version because a linker-visible symbol is affected. Old C code will still compile -- there's a b/w compat macro. Similarly, old Python code will still run, builtin exports both Ellipses and Ellipsis.
1996-10-11 16:25:41 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
30-Jul-1996 GvR Slice and ellipses syntax added
Two bumps for the price of one (PYTHON_API_VERSION)
1996-07-30 16:41:02 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
23-Jul-1996 GvR For 1.4 -- better safe than sorry this time :-)
Two bumps for the price of one (PYTHON_API_VERSION)
1996-07-30 16:41:02 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
7-Nov-1995 GvR Keyword arguments (should've been done at 1.3 :-( )
bump api version
1996-01-12 00:49:39 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
10-Jan-1995 GvR Renamed globals to new naming scheme
The great renaming, phase two: all header files have been updated to use the new names exclusively, and the linker will see the new names. Files that import "Python.h" also only see the new names. Files that import "allobjects.h" will continue to be able to use the old names, due to the inclusion (in allobjects.h) of "rename2.h".
1995-01-12 11:45:45 +00:00
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
9-Jan-1995 GvR Initial version (incompatible with older API)
api version checking
1995-01-09 17:47:20 +00:00
*/
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
/* The PYTHON_ABI_VERSION is introduced in PEP 384. For the lifetime of
Python 3, it will stay at the value of 3; changes to the limited API
must be performed in a strictly backwards-compatible manner. */
#define PYTHON_ABI_VERSION 3
#define PYTHON_ABI_STRING "3"
Add PYTHON_API_STRING, which is PYTHON_API_VERSION as a string literal. Under Windows, add MS_DLL_ID and MS_DLL_VERSION_ID for Mark H. Independent change: if Py_TRACE_REFS is defined, rename Py_InitModule4 so so linking with incompatible modules will create a link time error. [Backing out of previous changes (also for modsupport.c) to test the latter at runtime.]
1996-08-22 22:55:47 +00:00
#ifdef Py_TRACE_REFS
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
/* When we are tracing reference counts, rename module creation functions so
Merge ssize_t branch.
2006-02-15 17:27:45 +00:00
modules compiled with incompatible settings will generate a
link-time error. */
#5735: Modules compiled with incompatible settings (--with-pydebug when python is not) should generate a link-time error. I won't backport to 3.0, because it breaks binary compatibility
2009-06-01 21:16:17 +00:00
#define PyModule_Create2 PyModule_Create2TraceRefs
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
#define PyModule_FromDefAndSpec2 PyModule_FromDefAndSpec2TraceRefs
Add PYTHON_API_STRING, which is PYTHON_API_VERSION as a string literal. Under Windows, add MS_DLL_ID and MS_DLL_VERSION_ID for Mark H. Independent change: if Py_TRACE_REFS is defined, rename Py_InitModule4 so so linking with incompatible modules will create a link time error. [Backing out of previous changes (also for modsupport.c) to test the latter at runtime.]
1996-08-22 22:55:47 +00:00
#endif
Implement PEP 3121: new module initialization and finalization API.
2008-06-11 05:26:20 +00:00
PyAPI_FUNC(PyObject *) PyModule_Create2(struct PyModuleDef*,
int apiver);
* Added support for X11 modules. * Makefile: change location of FORMS library. * posixmodule.c: turn #if 0 into #ifdef MSDOS (stuff in unistd.h or not) * Almost all .h files: added CPP magic to avoid duplicate inclusions and to support inclusion from C++.
1993-07-28 09:05:47 +00:00
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
#ifdef Py_LIMITED_API
#define PyModule_Create(module) \
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
PyModule_Create2(module, PYTHON_ABI_VERSION)
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
#else
Implement PEP 3121: new module initialization and finalization API.
2008-06-11 05:26:20 +00:00
#define PyModule_Create(module) \
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
PyModule_Create2(module, PYTHON_API_VERSION)
#endif
Issue 24365: Conditionalize PEP 489 additions to the stable ABI Patch by Petr Viktorin.
2015-06-02 23:06:47 +00:00
#if !defined(Py_LIMITED_API) || Py_LIMITED_API+0 >= 0x03050000
/* New in 3.5 */
PEP 489: Multi-phase extension module initialization Known limitations of the current implementation: - documentation changes are incomplete - there's a reference leak I haven't tracked down yet The leak is most visible by running: ./python -m test -R3:3 test_importlib However, you can also see it by running: ./python -X showrefcount Importing the array or _testmultiphase modules, and then deleting them from both sys.modules and the local namespace shows significant increases in the total number of active references each cycle. By contrast, with _testcapi (which continues to use single-phase initialisation) the global refcounts stabilise after a couple of cycles.
2015-05-23 12:24:10 +00:00
PyAPI_FUNC(PyObject *) PyModule_FromDefAndSpec2(PyModuleDef *def,
PyObject *spec,
int module_api_version);
#ifdef Py_LIMITED_API
#define PyModule_FromDefAndSpec(module, spec) \
PyModule_FromDefAndSpec2(module, spec, PYTHON_ABI_VERSION)
#else
#define PyModule_FromDefAndSpec(module, spec) \
PyModule_FromDefAndSpec2(module, spec, PYTHON_API_VERSION)
Issue 24365: Conditionalize PEP 489 additions to the stable ABI Patch by Petr Viktorin.
2015-06-02 23:06:47 +00:00
#endif /* Py_LIMITED_API */
#endif /* New in 3.5 */
Define new macro Py_InitModule3(name, methods, doc) which calls Py_InitModule4() with appropriate arguments.
1998-06-27 18:21:59 +00:00
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
#ifndef Py_LIMITED_API
Excise DL_EXPORT from Include. Thanks to Skip Montanaro and Kalle Svensson for the patches.
2002-08-12 07:21:58 +00:00
PyAPI_DATA(char *) _Py_PackageContext;
Merge branches/pep-0384.
2010-12-03 20:14:31 +00:00
#endif
Add declaration for _Py_PackageContext -- needed to fix importing of shared libraries from inside packages.
1997-11-19 18:51:35 +00:00
* Added support for X11 modules. * Makefile: change location of FORMS library. * posixmodule.c: turn #if 0 into #ifdef MSDOS (stuff in unistd.h or not) * Almost all .h files: added CPP magic to avoid duplicate inclusions and to support inclusion from C++.
1993-07-28 09:05:47 +00:00
#ifdef __cplusplus
}
#endif
#endif /* !Py_MODSUPPORT_H */