| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
| |
|
|
|
|
| |
of the init_socket() function. This module is now *always* _socket.
|
|
|
|
|
|
|
|
|
| |
Minor updates for BeOS R5.
Use of OSError in test.test_fork1 changed to TestSkipped, with corresponding
change in BeOS/README (by Fred).
This closes SourceForge patch #100978.
|
|
|
|
|
|
| |
in binascii.c (only on platforms with signed chars -- although Py_CHARMASK
is documented as returning an int, it only does so on platforms with
signed chars).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commonly used functions to convert an arbitrary binary string into
a hexadecimal digit representation and back again. These are often
(and often differently) implemented in Python. Best to have one
common fast implementation. Specifically,
binascii_hexlify(): a.k.a. b2a_hex() to return the hex representation
of binary data.
binascii_unhexlify(): a.k.a. a2b_hex() to do the inverse conversion
(hex digits to binary data). The argument must have an even length,
and must contain only hex digits, otherwise a TypeError is raised.
|
|
|
|
|
|
|
| |
after a brief conversation with TP. First, the return values of the
PyString_* function calls should be checked for errors. Second,
bit-manipulations should be used instead of division for spliting the
byte up into its 4 bit digits.
|
|
|
|
| |
to this module to mirror sha's hexdigest() method.
|
|
|
|
| |
The existing win32_error() function now returns the new(ish) WindowsError, ensuring we get correct error messages.
|
|
|
|
|
| |
This is an enhancement to a prior patch (100941) ...
[T]his patch removes the risk of deadlock waiting for the child previously present in certain cases. It adds tracking of all file handles returned from an os.popen* call and only waits for the child process, returning the exit code, on the closure of the final file handle to that child.
|
|
|
|
|
| |
and fwrite return size_t, so it is safer to cast up to the largest type for the
comparison. I believe the cast is required at all to remove compiler warnings.
|