summaryrefslogtreecommitdiffstats
path: root/Python
Commit message (Collapse)AuthorAgeFilesLines
* Prepare for 2.3.7c1.v2.3.7c1Martin v. Löwis2008-03-021-1/+1
|
* Backport of r61180:Martin v. Löwis2008-03-021-4/+56
| | | | | | Added checks for integer overflows, contributed by Google. Some are only available if asserts are left in the code, in cases where they can't be triggered from Python code.
* Partially revert #1074011; don't try to fflush stdin.Martin v. Löwis2005-01-271-1/+10
|
* happy new year!Anthony Baxter2005-01-251-1/+1
|
* Flush std{in,out,err} before closing it. Fixes #1074011.Martin v. Löwis2005-01-231-3/+10
|
* backport: make thread stack size compile-time tunable on OS/2Andrew MacIntyre2005-01-171-1/+5
|
* Taken from 2.4/HEAD:Matthias Klose2004-12-011-0/+6
| | | | | | - Bug #875692: Improve signal handling, especially when using threads, by forcing an early re-execution of PyEval_EvalFrame() "periodic" code when things_to_do is not cleared by Py_MakePendingCalls().
* Backported thread fixes from 2.4 (by mostly copying pystate.c over from 2.4):Armin Rigo2004-11-092-66/+182
| | | | | | | * using malloc() and free() directly, as explained in the new comment * coding style in the PyGILState_*() functions * the recent destroy-tstate-without-holding-the-GIL bug * lock fixes and many more comments in thread.c
* Fix for SF bug #1029475 : reload() doesn't work with PEP 302 loaders.Phillip J. Eby2004-09-231-4/+7
| | | | (Backport to 2.3 maintenance branch.)
* Patch #1015021: Stop claiming that coerce can return None.Martin v. Löwis2004-08-251-4/+4
|
* Backport SF bug #1004088:Raymond Hettinger2004-08-061-0/+4
| | | | big code objects (>64K) may be optimized incorrectly
* Patch #984714: Properly diagnose E_DECODE errors.Martin v. Löwis2004-07-211-0/+3
|
* When importing an extension on Windows, the code reads the PE 'importThomas Heller2004-07-021-0/+12
| | | | | | | | | | | | | | | | table' of the dll, to make sure that the dll really was build for the correct Python version. It does this by looking for an entry 'pythonXY.dll' (X.Y is the Python version number). The code now checks the size of the dll's import table before reading entries from it. Before this patch, the code crashed trying to read the import table when the size was zero (as in Win2k's wmi.dll, for example). Look for imports of 'pythonXY_d.dll' in a debug build instead of 'pythonXY.dll'. Fixes SF 951851: Crash when reading "import table" of certain windows dlls.
* Fix a refcount bug in an obscure code corner.Thomas Heller2004-06-071-0/+1
|
* better yetAnthony Baxter2004-05-131-1/+1
|
* how many @*&(*$# places do we include the years??Anthony Baxter2004-05-131-1/+1
|
* OS/2 VACPP build updates/fixesAndrew MacIntyre2004-03-291-1/+1
|
* Decref all if ensure_fromlist fails. Fixes #876533.Martin v. Löwis2004-03-231-2/+3
|
* Backport for bug fix of 2.204.Armin Rigo2004-03-221-6/+8
|
* Remove the PendingDeprecationWarning from apply(). apply() willFred Drake2003-12-051-4/+0
| | | | remain deprecated in the documentation.
* Py_Finalize(): disabled the second call of cyclic gc, and added extensiveTim Peters2003-12-011-2/+27
| | | | | | | comments about why both calls to cyclic gc here can cause problems. Already fixed on the trunk. Since the calls were introduced in 2.3, that's the end of it.
* Patch #804543: strdup saved locales.Martin v. Löwis2003-11-131-1/+2
|
* regressing the performance bugfix -- Guido wants the performance bug leftAlex Martelli2003-10-251-1/+1
| | | | alone, because there can be no guarantee re the semantics of += vs + .
* changed builtin_sum to use PyNumber_InPlaceAdd -- unchanged semantics butAlex Martelli2003-10-251-1/+1
| | | | fixes performance bug with sum(lotsoflists, []).
* Backport checkin:Walter Dörwald2003-10-201-1/+1
| | | | | Fix a bunch of typos in documentation, docstrings and comments. (From SF patch #810751)
* Backport fix for SF808594: leak on lambda with duplicate arguments.Jeremy Hylton2003-09-221-15/+16
|
* Patch #805613: Fix usage of the PTH library.Martin v. Löwis2003-09-202-1/+7
|
* Backport leak fix for new code objects.Raymond Hettinger2003-09-161-17/+16
|
* Patch #794826: Add __file__ in dynamically loaded modules for multipleMartin v. Löwis2003-09-041-2/+3
| | | | interpreters. Fixes #698282.
* Backport checkin:Walter Dörwald2003-08-181-3/+10
| | | | | | | Fix a crash: when sq_item failed the code continued blindly and used the NULL pointer. (Detected by Michael Hudson, patch provided by Neal Norwitz). Fix refcounting leak in filtertuple().
* Backport checkin:Walter Dörwald2003-08-141-1/+1
| | | | | | Fix refcount leak in the UnicodeError constructor: When parsing the constructor arguments failed, a reference to the argument tuple was leaked.
* Backport checkins:Walter Dörwald2003-08-121-5/+21
| | | | | | | | * Enhance message for UnicodeEncodeError and UnicodeTranslateError. If there is only one bad character it will now be printed in a form that is a valid Python string. * Add a unicode prefix to the characters in the UnicodeEncodeError and UnicodeTranslateError message.
* Repeat my refcount & cut&paste fixes on the branch.Michael W. Hudson2003-08-111-3/+1
|
* Move initialization of sys.std{in,out}.encoding to Py_Initialize.Martin v. Löwis2003-08-092-33/+51
| | | | Verify that the encoding actually exists. Fixes #775985.
* Patch 775605: Cygwin pthread_sigmask() workaround patchJason Tishler2003-07-221-1/+1
| | | | | | | | | | | | | | | | | | Cygwin's pthread_sigmask() implementation appears to be buggy. This patch works around this problem by using sigprocmask() instead. This patch is implemented in a general way so it could be used by other platforms too. If this approach is deemed too risky, then I can work up a patch that just hacks Python/thread_pthread.h for Cygwin. Note that I tested this patch against 2.3c1 under Red Hat Linux 8.0 too. [snip] And finally, I need someone to regenerate pyconfig.h.in and configure with the same versions of the autotools that are normally used by Python. Neal kindly regenerated pyconfig.h.in and configure for me.
* Correct previous patch looking for warnings module: sys.modules, notMark Hammond2003-07-161-1/+1
| | | | sys.__modules__.
* Fix [ 771097 ] frozen programs fail due to implicit import of "warnings".Mark Hammond2003-07-152-8/+40
| | | | | | If the initial import of warnings fails, clear the error. When the module is actually needed, if the original import failed, see if it has managed to find its way to sys.modules yet and if so, remember it.
* SF patch 763201: handling of SyntaxErrors in symbol table buildJeremy Hylton2003-07-151-33/+47
| | | | | | | | | | | | | | Fixes for three related bugs, including errors that caused a script to be ignored without printing an error message. The key problem was a bad interaction between syntax warnings and syntax errors. If an exception was already set when a warning was issued, the warning could clobber the exception. The PyErr_Occurred() check in issue_warning() isn't entirely satisfying (the caller should know whether there was already an error), but a better solution isn't immediately obvious. Bug fix candidate.
* Initialize thread_id to 0 in unthreaded build. Fixes #770247.Martin v. Löwis2003-07-131-0/+4
|
* - fix typoFred Drake2003-07-111-1/+1
| | | | | - there's a weird variable name here (zimpimport), but I'll leave that for someone that's familiar with the ZIP import support
* New function sys.getcheckinterval(), to complement setcheckinterval().Tim Peters2003-07-061-0/+12
|
* An Anonymous Coward on c.l.py posted a little program with bizarreTim Peters2003-07-041-23/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | behavior, creating many threads very quickly. A long debugging session revealed that the Windows implementation of PyThread_start_new_thread() was choked with "laziness" errors: 1. It checked MS _beginthread() for a failure return, but when that happened it returned heap trash as the function result, instead of an id of -1 (the proper error-return value). 2. It didn't consider that the Win32 CreateSemaphore() can fail. 3. When creating a great many threads very quickly, it's quite possible that any particular bootstrap call can take virtually any amount of time to return. But the code waited for a maximum of 5 seconds, and didn't check to see whether the semaphore it was waiting for got signaled. If it in fact timed out, the function could again return heap trash as the function result. This is actually what confused the test program, as the heap trash usually turned out to be 0, and then multiple threads all got id 0 simultaneously, confusing the hell out of threading.py's _active dict (mapping id to thread object). A variety of baffling behaviors followed from that. WRT #1 and #2, error returns are checked now, and "thread.error: can't start new thread" gets raised now if a new thread (or new semaphore) can't be created. WRT #3, we now wait for the semaphore without a timeout. Also removed useless local vrbls, folded long lines, and changed callobj to a stack auto (it was going thru malloc/free instead, for no discernible reason). Bugfix candidate.
* Fix SF #762455, segfault when sys.stdout is changed in getattrNeal Norwitz2003-06-291-0/+6
| | | | Will backport.
* Add PyThreadState_SetAsyncExc(long, PyObject *).Guido van Rossum2003-06-282-1/+47
| | | | | | | | | A new API (only accessible from C) to interrupt a thread by sending it an exception. This is not always effective, but might help some people. Requested by Just van Rossum and Alex Martelli. It is intentional that you have to write your own C extension to call it from Python. Docs will have to wait.
* Better error messageJeremy Hylton2003-06-211-1/+7
|
* Removed bytecode transformation for sequence packing/unpacking.Raymond Hettinger2003-06-201-28/+0
| | | | | | | It depended on the previously removed basic block checker to prevent a jump into the middle of the transformed block. Clears SF 757818: tuple assignment -- SystemError: unknown opcode
* Don't use the module object setattr when importing submodules. Instead,Neil Schemenauer2003-06-161-18/+38
| | | | | | operate on the module dictionary directly. This prevents spurious depreciation warnings from being raised if a submodule name shadows a builtin name.
* Use fast_next_opcode shortcut for forward jump opcodes (it's safe andNeil Schemenauer2003-06-011-5/+5
| | | | gives a small speedup).
* SF bug #733667: kwargs handled incorrectlyRaymond Hettinger2003-05-311-1/+1
| | | | | The fast_function() inlining optimization only applies when there are zero keyword arguments.
* Don't use fast_next_opcode for JUMP_* opcodes. This fixes the problemNeil Schemenauer2003-05-301-6/+6
| | | | reported by Kurt B. Kaiser.
generated by cgit v0.12 at 2025-09-09 10:29:13 (GMT)