| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
declarations, added some comments where I had to think too hard to
understand what was happening, and changed the primary internal get/set
functions to assert they're passed objects of the correct type instead of
doing runtime tests for that (it's an internal error that "should never
happen", so it's good enough to check it only in the debug build).
|
|
|
|
|
| |
automatically if dbopen is found in libc or libdb. This closes patch
#101420
|
|
|
|
| |
this time!
|
|
|
|
|
|
| |
module when e.g. copy_reg.py doesn't exist. This caused a core dump.
This closes SF bug 112944.
|
| |
|
|
|
|
| |
"Type \"copyright\", \"credits\" or \"license\" for more information."
|
|
|
|
| |
None (as documented) from start/end/span. closes bug #113254
|
|
|
|
| |
This should match the situation in the 1.6b1 tree.
|
|
|
|
| |
out by Curtis Jensen on c.l.py and forwarded by Fredrik Lundh.
|
|
|
|
| |
not ever see!
|
|
|
|
| |
when PyDict_SetItemString() fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Py_FatalError() from module initialization functions. The importing
mechanism already checks for PyErr_Occurred() after module importation
and it Does The Right Thing.
Unfortunately, the following either were not compiled or tested by the
regression suite, due to issues with my development platform:
almodule.c
cdmodule.c
mpzmodule.c
puremodule.c
timingmodule.c
|
|
|
|
|
|
|
| |
implementation. You don't want to know. I've asked Guido to give this
a critical review (we agreed on the approach, but the implementation
proved more ... interesting ... than anticipated). This will almost
certainly be the highlight of Mark Hammond's day <wink>.
|
|
|
|
| |
we don't need to run gc frequently
|
|
|
|
| |
(leaving the rest of the modules for Barry)
|
|
|
|
|
| |
add sanity check to gc: if an exception occurs during GC, call
PyErr_WriteUnraisable and then call Py_FatalEror.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Linux. Perhaps winaudio would be better, as it would offend both
parties equally.
tg@freebsd.org: allow this module to compile under FreeBSD
(he suggests voxwareaudio)
|
|
|
|
|
|
| |
need to be checked to make sure all the latest information is present.
This closes SourceForge patch #101275.
|
|
|
|
|
|
|
|
|
|
|
| |
Update the build structures to automatically detect the presence of BSD db,
including the proper name of the header file to include. Has all the
expected niceties associated with yet-more-configure-options. ;)
This checkin includes changes for non-generated files only; subsequent
checkin will catch those.
This is part of SourceForge patch #101272.
|
|
|
|
| |
also initial static debug variable to 0
|
|
|
|
|
|
| |
Remove some of GCC's warning in -Wstrict-prototypes mode.
This closes SourceForge patch #101342.
|
| |
|
| |
|
|
|
|
|
|
|
| |
with success. also, check return values from the mark functions.
this addresses (but doesn't really solve) bug #112693, and low-memory
problems reported by jack jansen.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PyRun_FileEx(). These are the same as their non-Ex counterparts but
have an extra argument, a flag telling them to close the file when
done.
Then this is used by Py_Main() and execfile() to close the file after
it is parsed but before it is executed.
Adding APIs seems strange given the feature freeze but it's the only
way I see to close the bug report without incompatible changes.
[ Bug #110616 ] source file stays open after parsing is done (PR#209)
|
|
|
|
|
|
|
| |
fork. This solves the test_fork1 problem. (ceval.c, signalmodule.c,
intrcheck.c)
SourceForge: [ Patch #101226 ] make threading fork-safe
|
| |
|
|
|
|
|
|
| |
Windows "inconsistent linkage" warnings at the same time. I agree
with Mark Hammond that the whole DL_IMPORT/DL_EXPORT macro system
needs an overhaul; this is just an expedient hack until then.
|
|
|
|
| |
Add some test cases.
|
|
|
|
|
|
|
|
|
| |
Added prototype to remove yet another warning.
Make a number of the handlers and helpers "static" since they are not
used in other C source files. This also reduces the number of warnings.
Make a lot of the code "more Python". (Need to get the style guide done!)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
that this is not appropriate.
Made somewhat more robust in the face of reload() (exception is not
rebuilt, etc.).
Made the exception a class exception.
|
|
|
|
| |
Grammar file. This makes the test suite pass once again.
|
| |
|
|
|
|
|
|
| |
print statement), and fix up the extended call syntax support.
Minor stylistic cleanups.
|
| |
|
|
|
|
| |
Fix comment typo
|
| |
|
|
|
|
| |
have access to Purify anymore.
|
|
|
|
| |
been closed. Don't try to reclose it. Found by Insure.
|
|
|
|
|
| |
PyList_Append() always incref's the inserted item. Be sure to decref
it regardless of whether the append succeeds or fails.
|
|
|
|
| |
Py_FatalError() should reflect that.
|
|
|
|
|
|
|
|
|
| |
(64-bit AIX) This is because the RECURSION_LIMIT is too low. This patch lowers
to recusion limit to 7500 such that the recusion check fires before a segfault.
Fredrik suggested/approved the fix in private email, modulo sre's recusion
limit checking no being necessary when PyOS_CheckStack is implemented for
Windows.
|
| |
|