traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cpython/Include/Python.h

172 lines
4.1 KiB
C
Raw Normal View History

Several oopsies -- Py_ALLOBJECTS_H -> Py_PYTHON_H, temporarily removed pystate.h (to be restored later when that code is debugged), removed accessobject.h.
1997-05-02 01:00:11 -03:00
#ifndef Py_PYTHON_H
#define Py_PYTHON_H
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
/* Since this is a "meta-include" file, no #ifdef __cplusplus / extern "C" { */
/* Include nearly all Python header files */
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 08:40:24 -04:00
#include "patchlevel.h"
Patch #411138: Rename config.h to pyconfig.h. Closes bug #231774.
2001-07-26 10:41:06 -03:00
#include "pyconfig.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
Removed WITH_CYCLE_GC #ifdef-ery. Holes: + I'm not sure what to do about configure.in. Left it alone. + Ditto pyexpat.c. Fred or Martin will know what to do.
2002-07-07 00:59:34 -03:00
/* Cyclic gc is always enabled, starting with release 2.3a1. Supply the
* old symbol for the benefit of extension modules written before then
* that may be conditionalizing on it. The core doesn't use it anymore.
*/
#ifndef WITH_CYCLE_GC
#define WITH_CYCLE_GC 1
#endif
Rationalize use of limits.h, moving the inclusion to Python.h. Add definitions of INT_MAX and LONG_MAX to pyport.h. Remove includes of limits.h and conditional definitions of INT_MAX and LONG_MAX elsewhere. This closes SourceForge patch #101659 and bug #115323.
2000-09-26 02:46:01 -03:00
#include <limits.h>
There are places in Python which assume bytes have 8-bits. Formalize that a bit by checking the value of UCHAR_MAX in Include/Python.h. There was a check in Objects/stringobject.c. Remove that. (Note that we don't define UCHAR_MAX if it's not defined as the old test did.)
2003-12-22 12:31:41 -04:00
#ifndef UCHAR_MAX
#error "Something's broken. UCHAR_MAX should be defined in limits.h."
#endif
#if UCHAR_MAX != 255
Changed the UCHAR_MAX error msg a bit: we don't really assume anything about "characters", we assume something about C's char type (which is an integral type).
2003-12-22 14:10:51 -04:00
#error "Python's source code assumes C's unsigned char is an 8-bit type."
There are places in Python which assume bytes have 8-bits. Formalize that a bit by checking the value of UCHAR_MAX in Include/Python.h. There was a check in Objects/stringobject.c. Remove that. (Note that we don't define UCHAR_MAX if it's not defined as the old test did.)
2003-12-22 12:31:41 -04:00
#endif
On SGI, we need to define _SGI_MP_SOURCE before including errno.h when we are threading, otherwise accessing errno doesn't work right.
1998-05-26 15:38:07 -03:00
#if defined(__sgi) && defined(WITH_THREAD) && !defined(_SGI_MP_SOURCE)
#define _SGI_MP_SOURCE
#endif
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include <stdio.h>
Close SF bug 110826: a complaint about the way Python #define'd NULL. It's hard to sort out what the bug was, exactly. So, Big Hammer: 1. Python shouldn't be in the business of #define'ing NULL, period. 2. Users of the Python C API shouldn't be in the business of not including Python.h, period. Hence: 1. Removed all #define's of NULL in Python source code (pyport.h and object.h). 2. Since we're *relying* on stdio.h defining NULL, put an #error in Python.h after its #include of stdio.h if NULL isn't defined then.
2000-09-09 22:02:41 -03:00
#ifndef NULL
# error "Python.h requires that stdio.h define NULL."
#endif
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include <string.h>
#include <errno.h>
#include <stdlib.h>
Include <unistd.h> in Python.h. Fixes #500924.
2002-01-12 07:05:12 -04:00
#ifdef HAVE_UNISTD_H
#include <unistd.h>
#endif
Define NDEBUG when Py_DEBUG undefined, to disable the assert macro.
2001-07-15 13:58:05 -03:00
Use intptr_t/uintptr_t on Windows
2004-07-27 12:57:24 -03:00
/* For uintptr_t, intptr_t */
#ifdef HAVE_STDDEF_H
#include <stddef.h>
#endif
Stop defining NDEBUG in Python.h, because it can interfere with extensions that #include Python.h. See (rejected) patch 487634 for more detail. I'll open a new bug report for the rest needed here.
2001-12-04 16:06:11 -04:00
/* CAUTION: Build setups should ensure that NDEBUG is defined on the
* compiler command line when building Python in release mode; else
* assert() calls won't be removed.
*/
Included assert.h in Python.h -- it's absurd that this basic tool of good C practice hasn't been available to everything all along. Added Py_SAFE_DOWNCAST(VALUE, WIDE, NARROW) macro to pyport.h; this just casts VALUE from type WIDE to type NARROW, but assert-fails if Py_DEBUG is defined and info is lost due to casting. Replaced a line in Fredrik's fix to marshal.c to use the new macro.
2000-07-23 16:28:35 -03:00
#include <assert.h>
Back out #555929
2002-05-15 15:24:06 -03:00
#include "pyport.h"
Patch #555929: Cygwin AH_BOTTOM cleanup patch (*** version 2 ***) This patch complies with the following request found near the top of configure.in: # This is for stuff that absolutely must end up in pyconfig.h. # Please use pyport.h instead, if possible. I tested this patch under Cygwin, Win32, and Red Hat Linux. Python built and ran successfully on each of these platforms.
2002-06-04 12:07:08 -03:00
/* pyconfig.h or pyport.h may or may not define DL_IMPORT */
#ifndef DL_IMPORT /* declarations for DLL import/export */
#define DL_IMPORT(RTYPE) RTYPE
#endif
#ifndef DL_EXPORT /* declarations for DLL import/export */
#define DL_EXPORT(RTYPE) RTYPE
#endif
Give Python a debug-mode pymalloc, much as sketched on Python-Dev. When WITH_PYMALLOC is defined, define PYMALLOC_DEBUG to enable the debug allocator. This can be done independent of build type (release or debug). A debug build automatically defines PYMALLOC_DEBUG when pymalloc is enabled. It's a detected error to define PYMALLOC_DEBUG when pymalloc isn't enabled. Two debugging entry points defined only under PYMALLOC_DEBUG: + _PyMalloc_DebugCheckAddress(const void *p) can be used (e.g., from gdb) to sanity-check a memory block obtained from pymalloc. It sprays info to stderr (see next) and dies via Py_FatalError if the block is detectably damaged. + _PyMalloc_DebugDumpAddress(const void *p) can be used to spray info about a debug memory block to stderr. A tiny start at implementing "API family" checks isn't good for anything yet. _PyMalloc_DebugRealloc() has been optimized to do little when the new size is <= old size. However, if the new size is larger, it really can't call the underlying realloc() routine without either violating its contract, or knowing something non-trivial about how the underlying realloc() works. A memcpy is always done in this case. This was a disaster for (and only) one of the std tests: test_bufio creates single text file lines up to a million characters long. On Windows, fileobject.c's get_line() uses the horridly funky getline_via_fgets(), which keeps growing and growing a string object hoping to find a newline. It grew the string object 1000 bytes each time, so for a million-character string it took approximately forever (I gave up after a few minutes). So, also: fileobject.c, getline_via_fgets(): When a single line is outrageously long, grow the string object at a mildly exponential rate, instead of just 1000 bytes at a time. That's enough so that a debug-build test_bufio finishes in about 5 seconds on my Win98SE box. I'm curious to try this on Win2K, because it has very different memory behavior than Win9X, and test_bufio always took a factor of 10 longer to complete on Win2K. It *could* be that the endless reallocs were simply killing it on Win2K even in the release build.
2002-03-23 06:03:50 -04:00
/* Debug-mode build with pymalloc implies PYMALLOC_DEBUG.
* PYMALLOC_DEBUG is in error if pymalloc is not in use.
*/
#if defined(Py_DEBUG) && defined(WITH_PYMALLOC) && !defined(PYMALLOC_DEBUG)
#define PYMALLOC_DEBUG
#endif
#if defined(PYMALLOC_DEBUG) && !defined(WITH_PYMALLOC)
#error "PYMALLOC_DEBUG requires WITH_PYMALLOC"
#endif
patch from Vladimir (move Py_Mem* interface to Include/pymem.h)
2000-07-31 19:19:30 -03:00
#include "pymem.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "object.h"
#include "objimpl.h"
#include "pydebug.h"
Marc-Andre's third try at this bulk patch seems to work (except that his copy of test_contains.py seems to be broken -- the lines he deleted were already absent). Checkin messages: New Unicode support for int(), float(), complex() and long(). - new APIs PyInt_FromUnicode() and PyLong_FromUnicode() - added support for Unicode to PyFloat_FromString() - new encoding API PyUnicode_EncodeDecimal() which converts Unicode to a decimal char* string (used in the above new APIs) - shortcuts for calls like int(<int object>) and float(<float obj>) - tests for all of the above Unicode compares and contains checks: - comparing Unicode and non-string types now works; TypeErrors are masked, all other errors such as ValueError during Unicode coercion are passed through (note that PyUnicode_Compare does not implement the masking -- PyObject_Compare does this) - contains now works for non-string types too; TypeErrors are masked and 0 returned; all other errors are passed through Better testing support for the standard codecs. Misc minor enhancements, such as an alias dbcs for the mbcs codec. Changes: - PyLong_FromString() now applies the same error checks as does PyInt_FromString(): trailing garbage is reported as error and not longer silently ignored. The only characters which may be trailing the digits are 'L' and 'l' -- these are still silently ignored. - string.ato?() now directly interface to int(), long() and float(). The error strings are now a little different, but the type still remains the same. These functions are now ready to get declared obsolete ;-) - PyNumber_Int() now also does a check for embedded NULL chars in the input string; PyNumber_Long() already did this (and still does) Followed by: Looks like I've gone a step too far there... (and test_contains.py seem to have a bug too). I've changed back to reporting all errors in PyUnicode_Contains() and added a few more test cases to test_contains.py (plus corrected the join() NameError).
2000-04-05 17:11:21 -03:00
#include "unicodeobject.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "intobject.h"
Add the 'bool' type and its values 'False' and 'True', as described in PEP 285. Everything described in the PEP is here, and there is even some documentation. I had to fix 12 unit tests; all but one of these were printing Boolean outcomes that changed from 0/1 to False/True. (The exception is test_unicode.py, which did a type(x) == type(y) style comparison. I could've fixed that with a single line using issubtype(x, type(y)), but instead chose to be explicit about those places where a bool is expected. Still to do: perhaps more documentation; change standard library modules to return False/True from predicates.
2002-04-03 18:41:51 -04:00
#include "boolobject.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "longobject.h"
#include "floatobject.h"
#ifndef WITHOUT_COMPLEX
#include "complexobject.h"
#endif
#include "rangeobject.h"
#include "stringobject.h"
Add Greg Stein's buffer object API.
1998-10-07 11:36:10 -03:00
#include "bufferobject.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "tupleobject.h"
#include "listobject.h"
Subsumed mappingobject.h in dictobject.h.
1997-05-13 18:23:32 -03:00
#include "dictobject.h"
- New builtin function enumerate(x), from PEP 279. Example: enumerate("abc") is an iterator returning (0,"a"), (1,"b"), (2,"c"). The argument can be an arbitrary iterable object.
2002-04-26 16:40:56 -03:00
#include "enumobject.h"
* Migrate set() and frozenset() from the sandbox. * Install the unittests, docs, newsitem, include file, and makefile update. * Exercise the new functions whereever sets.py was being used. Includes the docs for libfuncs.tex. Separate docs for the types are forthcoming.
2003-11-16 12:17:49 -04:00
#include "setobject.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "methodobject.h"
#include "moduleobject.h"
#include "funcobject.h"
#include "classobject.h"
#include "fileobject.h"
#include "cobject.h"
#include "traceback.h"
#include "sliceobject.h"
PEP 227 implementation A cell contains a reference to a single PyObject. It could be implemented as a mutable, one-element sequence, but the separate type has less overhead.
2001-01-25 16:04:14 -04:00
#include "cellobject.h"
Iterators phase 1. This comprises: new slot tp_iter in type object, plus new flag Py_TPFLAGS_HAVE_ITER new C API PyObject_GetIter(), calls tp_iter new builtin iter(), with two forms: iter(obj), and iter(function, sentinel) new internal object types iterobject and calliterobject new exception StopIteration new opcodes for "for" loops, GET_ITER and FOR_ITER (also supported by dis.py) new magic number for .pyc files new special method for instances: __iter__() returns an iterator iteration over dictionaries: "for x in dict" iterates over the keys iteration over files: "for x in file" iterates over lines TODO: documentation test suite decide whether to use a different way to spell iter(function, sentinal) decide whether "for key in dict" is a good idea use iterators in map/filter/reduce, min/max, and elsewhere (in/not in?) speed tuning (make next() a slot tp_next???)
2001-04-20 16:13:02 -03:00
#include "iterobject.h"
Patch #966493: Cleanup generator/eval_frame exposure.
2004-06-27 12:43:12 -03:00
#include "genobject.h"
Merge of descr-branch back into trunk.
2001-08-02 01:15:00 -03:00
#include "descrobject.h"
Include the weakref object interface.
2001-10-05 18:55:19 -03:00
#include "weakrefobject.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
Marc-Andre Lemburg: include unicodeobject.h and codecs.h
2000-03-10 18:34:00 -04:00
#include "codecs.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "pyerrors.h"
Include pystate.h earlier so it can be referenced by ceval.h.
1997-07-18 20:59:26 -03:00
#include "pystate.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "modsupport.h"
#include "pythonrun.h"
Part way to allowing "from __future__ import generators" to communicate that info to code dynamically compiled *by* code compiled with generators enabled. Doesn't yet work because there's still no way to tell the parser that "yield" is OK (unlike nested_scopes, the parser has its fingers in this too). Replaced PyEval_GetNestedScopes by a more-general PyEval_MergeCompilerFlags. Perhaps I should not have? I doubted it was *intended* to be part of the public API, so just did.
2001-07-15 23:29:45 -03:00
#include "ceval.h"
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#include "sysmodule.h"
#include "intrcheck.h"
#include "import.h"
#include "abstract.h"
compile.h and eval.h weren't being included which kept a fair bit of the public API from being exposed by simply including Python.h (as recommended).
2004-03-13 19:11:44 -04:00
#include "compile.h"
#include "eval.h"
Patch #774665: Make Python LC_NUMERIC agnostic.
2004-06-08 15:52:54 -03:00
#include "pystrtod.h"
SF 569257 -- Name mangle double underscored variable names in __slots__.
2002-06-20 19:23:15 -03:00
/* _Py_Mangle is defined in compile.c */
Excise DL_EXPORT from Include. Thanks to Skip Montanaro and Kalle Svensson for the patches.
2002-08-12 04:21:58 -03:00
PyAPI_FUNC(int) _Py_Mangle(char *p, char *name, \
SF 569257 -- Name mangle double underscored variable names in __slots__.
2002-06-20 19:23:15 -03:00
char *buffer, size_t maxlen);
Add a comment that PyArg_GetInt is deprecated and should not be used
2002-03-25 18:21:58 -04:00
/* PyArg_GetInt is deprecated and should not be used, use PyArg_Parse(). */
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#define PyArg_GetInt(v, a) PyArg_Parse((v), "i", (a))
Remove many uses of PyArg_NoArgs macro, change METH_OLDARGS to METH_NOARGS.
2002-03-25 16:46:46 -04:00
/* PyArg_NoArgs should not be necessary.
Set ml_flags in the PyMethodDef to METH_NOARGS. */
Moved allobjects.h to Python.h (without rename2.h). allobjects.h disappears -- old-style extensions must include Python.h and rename2.h.
1997-05-02 00:55:52 -03:00
#define PyArg_NoArgs(v) PyArg_Parse(v, "")
/* Convert a possibly signed character to a nonnegative int */
/* XXX This assumes characters are 8 bits wide */
#ifdef __CHAR_UNSIGNED__
#define Py_CHARMASK(c) (c)
#else
#define Py_CHARMASK(c) ((c) & 0xff)
#endif
#include "pyfpe.h"
Typo fix in comment.
2000-05-28 17:29:48 -03:00
/* These definitions must match corresponding definitions in graminit.h.
Instead of importing graminit.h whenever one of the three grammar 'root' symbols is needed, define these in Python.h with a Py_ prefix.
1997-05-07 14:46:13 -03:00
There's code in compile.c that checks that they are the same. */
#define Py_single_input 256
#define Py_file_input 257
#define Py_eval_input 258
Make better use of GNU Pth -- patch by Andy Dustman. I can't test this, so I'm just checking it in with blind faith in Andy. I've tested that it doesn't broeak a non-Pth build on Linux. Changes include: - There's a --with-pth configure option. - Instead of _GNU_PTH, we test for HAVE_PTH. - Better signal handling. - (The config.h.in file is regenerated in a slightly different order.)
2000-09-18 21:46:46 -03:00
#ifdef HAVE_PTH
Andy Dustman: add GNU pth user-space thread support.
2000-05-08 10:41:38 -03:00
/* GNU pth user-space thread support */
#include <pth.h>
#endif
Patch #505375: Make doc strings optional.
2002-06-09 10:33:54 -03:00
/* Define macros for inline documentation. */
#define PyDoc_VAR(name) static char name[]
#define PyDoc_STRVAR(name,str) PyDoc_VAR(name) = PyDoc_STR(str)
#ifdef WITH_DOC_STRINGS
#define PyDoc_STR(str) str
#else
#define PyDoc_STR(str) ""
#endif
Several oopsies -- Py_ALLOBJECTS_H -> Py_PYTHON_H, temporarily removed pystate.h (to be restored later when that code is debugged), removed accessobject.h.
1997-05-02 01:00:11 -03:00
#endif /* !Py_PYTHON_H */