summaryrefslogtreecommitdiffstats
path: root/Include
Commit message (Collapse)AuthorAgeFilesLines
* Declarations related to new WindowsError exception.Guido van Rossum2000-02-171-0/+7
|
* The rest of the changes by Trent Mick and Dale Nagata for warning-freeGuido van Rossum2000-01-201-0/+1
| | | | compilation on NT Alpha. Mostly added casts etc.
* Mainlining the string_methods branch. See branch revision logBarry Warsaw1999-10-122-0/+2
| | | | messages for specific changes.
* Patch by Tim Peters:Guido van Rossum1999-06-221-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce a new builtin exception, UnboundLocalError, raised when ceval.c tries to retrieve or delete a local name that isn't bound to a value. Currently raises NameError, which makes this behavior a FAQ since the same error is raised for "missing" global names too: when the user has a global of the same name as the unbound local, NameError makes no sense to them. Even in the absence of shadowing, knowing whether a bogus name is local or global is a real aid to quick understanding. Example: D:\src\PCbuild>type local.py x = 42 def f(): print x x = 13 return x f() D:\src\PCbuild>python local.py Traceback (innermost last): File "local.py", line 8, in ? f() File "local.py", line 4, in f print x UnboundLocalError: x D:\src\PCbuild> Note that UnboundLocalError is a subclass of NameError, for compatibility with existing class-exception code that may be trying to catch this as a NameError. Unfortunately, I see no way to make this wholly compatible with -X (see comments in bltinmodule.c): under -X, [UnboundLocalError is an alias for NameError --GvR]. [The ceval.c patch differs slightly from the second version that Tim submitted; I decided not to raise UnboundLocalError for DELETE_NAME, only for DELETE_LOCAL. DELETE_NAME is only generated at the module level, and since at that level a NameError is raised for referencing an undefined name, it should also be raised for deleting one.]
* Set PATCHLEVEL and PY_VERSION (string version only) to 1.5.2+ toGuido van Rossum1999-06-091-2/+2
| | | | | | indicate to those that are using the CVS access that they are using a newer-than-1.2.5 version, without committing to a particular version number or patch level.
* Prepare for final release.Guido van Rossum1999-04-131-4/+5
|
* Release 1.5.2c1Guido van Rossum1999-04-081-4/+4
|
* Add the possibility of a gamma release (release candidate).Guido van Rossum1999-04-071-2/+3
| | | | Add '+' to string version number to indicate we're beyond b2 now.
* Conform to standard boilerplate.Guido van Rossum1999-03-241-3/+34
|
* Adding thread.h -- unused but for b/w compatibility.Guido van Rossum1999-03-221-0/+62
| | | | As requested by Bill Janssen.
* Add DLL level b/w compat for PySequence_In and PyEval_CallObjectGuido van Rossum1999-03-172-0/+10
|
* Add PyModule_GetFilename().Guido van Rossum1999-02-151-0/+1
|
* There's a macro PycString_IMPORT which the documentation listed asGuido van Rossum1999-01-251-1/+1
| | | | | | PycStringIO_IMPORT. While arguably the name used in the documentation is more consistent, I think it's probably safer not to change the macro definition and instead fix the doco.
* Changes for long file support by Steve Clift.Guido van Rossum1999-01-061-0/+19
|
* Chris Herborth writes:Guido van Rossum1999-01-041-5/+0
| | | | Donn Cave tells me the PyImport_BeImageID() function isn't needed anymore.
* New version identification scheme.Guido van Rossum1999-01-033-4/+74
| | | | | The version numbers are now exported by Python.h. Also rolled back the API version change -- it's back to 1007!
* I can't seem to do anything right :-)Guido van Rossum1998-12-211-1/+1
| | | | | As Chris H. points out, I should have added 'extern' to the declaration of _PyThreadState_Current. Here it is.
* Thanks to Chris Herborth, the thread primitives now have proper Py*Guido van Rossum1998-12-211-55/+21
| | | | | names in the source code (they already had those for the linker, through some smart macros; but the source still had the old, un-Py names).
* Add macro version of PyThreadState_GET(). This usesGuido van Rossum1998-12-211-0/+11
| | | | _PyThreadState_Current, defined in pystate.c.
* Add prototypes for PyOS_strto[u]l -- Chris Herborth.Guido van Rossum1998-12-101-0/+9
|
* Undo the change here -- there's no point in declaring a staticGuido van Rossum1998-12-081-1/+1
| | | | function as DL_IMPORT()!
* Add DL_IMPORT(returntype) for all officially exported functions.Guido van Rossum1998-12-0444-400/+403
|
* New API version (enough has changed!).Guido van Rossum1998-12-031-3/+5
|
* Added PyExc_NotImplementedErrorBarry Warsaw1998-12-011-0/+1
|
* Metrowerks PRO4 finally fixes the hypot snafu. (Jack Jansen)Guido van Rossum1998-11-021-1/+1
|
* Bump the patch level to 1.5.2b2, just in case I feel like releasingGuido van Rossum1998-10-241-1/+1
| | | | next week. :-)
* Changes by Greg Stein (code) and GvR (design).Guido van Rossum1998-10-081-2/+35
| | | | | | | | | | | | | | | | | | | | | | | | Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For backward compatibility, this member should only be used (this includes testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set in the type structure, below. Note that if its flag is not set, we may be looking at an extension module compiled for 1.5.1, which will have garbage at the bf_getcharbuffer member (because the struct wasn't as long then). If the flag is one, the pointer may still be NULL. The function found at this member is used in a similar manner as bf_getreadbuffer, but it is known to point to 8-bit character data. (See discussion in getargs.c checked in later.) As a general feature for extending the type structure and the various structures that (may) hang off it in a backwards compatible way, we rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before, this slot was always zero. In 1.5.1, it may contain various flags indicating extra fields that weren't present in 1.5.1. The only flag defined so far is for the bf_getcharbuffer member of the PyBufferProcs struct. Note that the new spares (tp_xxx5 - tp_xxx8), once they become used, should also be protected by a flag (or flags) in tp_flags.
* Changes to support other object types besides stringsGuido van Rossum1998-10-071-1/+6
| | | | | as the code string of code objects, as long as they support the (readonly) buffer interface. By Greg Stein.
* Add Greg Stein's buffer object API.Guido van Rossum1998-10-072-0/+62
|
* Up version to 1.5a2 -- we're close enough (even though I'm stillGuido van Rossum1998-10-021-1/+1
| | | | expecting some contributions).
* Renamed thread.h to pythread.h.Guido van Rossum1998-10-011-90/+0
|
* On second though, NEXITFUNCS should be defined in pythonrun.c and notGuido van Rossum1998-10-011-2/+0
| | | | | here; pystate.h doesn't use it (I thought I wanted to move the array there but that won't work).
* Move the #include of <sys/select> to *after* mytime.h (or <time.h>),Guido van Rossum1998-09-281-2/+2
| | | | as this is the logical order of dependencies. Suggested by Jeff Rush.
* Patches from Greg Stein to support 'P' format in struct module'sGuido van Rossum1998-09-181-0/+2
| | | | | native format, as void* (translated to Python int or long). Also adds PyLong_FromVoidPtr and PyLong_AsVoidPtr to longobject.c.
* Duplicate the decls for PySys_WriteStd{out,err} here so the VC++Guido van Rossum1998-09-171-0/+9
| | | | compiler doesn't grumble. Greg Stein's suggestion.
* Patch by Mark Hammond to support 64-bit ints on MS platforms.Guido van Rossum1998-08-251-4/+7
| | | | | | The MS compiler doesn't call it 'long long', it uses __int64, so a new #define, LONG_LONG, has been added and all occurrences of 'long long' are replaced with it.
* Move an indented #define to column 1.Guido van Rossum1998-08-231-1/+1
|
* Add missing prototypes for PyEval_CallFunction() and PyEval_CallMethod().Guido van Rossum1998-08-081-0/+10
|
* Upgrade patchlevel to 1.5.2a1.Guido van Rossum1998-08-051-1/+1
|
* Changes for BeOS, QNX and long long, by Chris Herborth.Guido van Rossum1998-08-044-0/+36
|
* New global variables: PyExc_EnvironmentError and PyExc_OSErrorBarry Warsaw1998-07-231-0/+3
| | | | New function: PyErr_SetFromErrnoWithFilename(PyObject* char*)
* Add macros for direct access to the members of CFunction objects.Guido van Rossum1998-07-101-0/+9
|
* Move the definition of PyMethodObject to classobject.h, so it can defineGuido van Rossum1998-07-101-0/+16
| | | | macros for more efficient access to the fields.
* Marc-Andre Lemburg's patch to move the typedef for PyCFunctionObjectGuido van Rossum1998-07-101-0/+15
| | | | to the .h file and add macros there for inlined access to the fields.
* Get rid of some obsolete opcodes.Guido van Rossum1998-07-071-5/+0
|
* Add PyImport_AppendInittab() an PyImport_ExtendInittab().Guido van Rossum1998-06-291-0/+3
|
* Define new macro Py_InitModule3(name, methods, doc) which callsGuido van Rossum1998-06-271-0/+4
| | | | Py_InitModule4() with appropriate arguments.
* On SGI, we need to define _SGI_MP_SOURCE before including errno.h whenGuido van Rossum1998-05-261-0/+4
| | | | we are threading, otherwise accessing errno doesn't work right.
* Renamed PySequence_In() to PySequence_Contains().Guido van Rossum1998-05-221-1/+2
|
* AddGuido van Rossum1998-05-121-0/+9
| | | | | PySys_WriteStdout(format, ...) PySys_WriteStderr(format, ...)
generated by cgit v0.12 at 2024-11-30 17:32:15 (GMT)