summaryrefslogtreecommitdiffstats
path: root/Misc
Commit message (Collapse)AuthorAgeFilesLines
* Make close() identical to __del__() for a dumbdbm database. MakeTim Peters2003-07-131-0/+3
| | | | | | | closing idempotent (it used to raise a nuisance exception on the 2nd close attempt). Bugfix candidate? Probably, but arguable.
* Repaired typos in comments.Tim Peters2003-07-131-1/+1
|
* Fixed critical shutdown race in _Database._commit.Tim Peters2003-07-131-0/+8
| | | | | | | | Related to SF patch 723231 (which pointed out the problem, but didn't fix it, just shut up the warning msg -- which was pointing out a dead- serious bug!). Bugfix candidate.
* Update for new module and new builtin.Raymond Hettinger2003-07-121-0/+3
|
* New function sys.getcheckinterval(), to complement setcheckinterval().Tim Peters2003-07-061-0/+3
|
* An Anonymous Coward on c.l.py posted a little program with bizarreTim Peters2003-07-041-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Correct documentation of check interval - it's 100 by default, not 10 anySkip Montanaro2003-07-021-1/+1
| | | | longer. Pointed out by Alex Martelli.
* Fix SF bug #763637, 2.3b2 unpack tuple of wrong size in after_cancelNeal Norwitz2003-07-011-0/+3
| | | | | Tk 8.4 may return different values than 8.3. This fix should handle either version.
* Make the classes exposed by threading.py new-style classes. This isTim Peters2003-07-011-0/+3
| | | | mostly for convenience and to aid debugging.
* Fix SF bug #763023, difflib.py: ratio() zero division not caughtNeal Norwitz2003-07-011-0/+3
| | | | Backport candidate
* Make temporary change of using _strptime for time.strptime permanent.Brett Cannon2003-07-011-0/+3
| | | | Flesh out docs to better explain time.strptime (closes bug #697990).
* SF bug 753592, websucker bugNeal Norwitz2003-07-011-0/+2
| | | | | Pass the proper variable when the user supplies a directory. Will backport.
* Fix SF 762891: "del p[key]" on proxy object raises SystemError()Raymond Hettinger2003-06-301-0/+33
|
* Merge branch updates back into the main trunkRaymond Hettinger2003-06-301-0/+40
|
* Add several news items for changes I made since b1.Jeremy Hylton2003-06-291-8/+36
|
* Removed XXX comments about missing threading.py functions.Tim Peters2003-06-291-4/+0
|
* Added news about os.environ['PYTHONINSPECT'] = 'yes'Barry Warsaw2003-06-291-0/+5
|
* Typo repair.Tim Peters2003-06-291-1/+1
|
* Provide dummy (do-nothing) settrace() and setprofile() functions untilTim Peters2003-06-291-0/+4
| | | | Jeremy can check in the real things.
* Filled in release date; repaired grammar in a news item.Tim Peters2003-06-291-3/+3
|
* Some nifty doctest extensions from Jim Fulton, currently used in Zope3.Tim Peters2003-06-291-0/+15
| | | | | | | | | I won't have time to write real docs, but spent a lot of time adding comments to his code and fleshing out the exported functions' docstrings. There's probably opportunity to consolidate how docstrings get extracted too, and the new code for that is probably better than the old code for that (which strained mightily to recover from 2.2's new class/type gimmicks).
* SF patch #760257: add socket.timeout exceptionRaymond Hettinger2003-06-291-0/+3
|
* Added Bob Halley for work on socket.timeoutRaymond Hettinger2003-06-291-0/+1
|
* Added Steven Taschuk for efforts fixing zipfile.pyRaymond Hettinger2003-06-281-0/+1
|
* SF patch #756996: Bare except in ZipFile.testzip()Raymond Hettinger2003-06-271-0/+4
| | | | | | | | | (Contributed by Steven Taschuk) Replaces a bare except that caused all errors to be mis-reported as archive errors. Added a related NEWS item.
* SF patch #761519: Fixes for bugs 760703 and 757821Raymond Hettinger2003-06-271-0/+3
| | | | | | | | | | | | | | | | | | SF bug #760703: SocketHandler and LogRecord don't work well together SF bug #757821: logging module docs Applied Vinay Sajip's patch with a few minor fixups and a NEWS item. Patched __init__.py - added new function makeLogRecord (for bug report 760703). Patched handlers.py - updated some docstrings and deleted some old commented-out code. Patched test_logging.py to make use of makeLogRecord. Patched liblogging.tex to fill documentation gaps (both 760703 and bug 757821).
* A hack to ease compatibility with pre-2.3 Pythons: by default, doctestTim Peters2003-06-271-0/+8
| | | | | | | | | | | | | | now accepts "True" when a test expects "1", and similarly for "False" versus "0". This is un-doctest-like, but on balance makes it much more pleasant to write doctests that pass under 2.2 and 2.3. I expect it to go away again, when 2.2 is forgotten. In the meantime, there's a new doctest module constant that can be passed to a new optional argument, if you want to turn this behavior off. Note that this substitution is very simple-minded: the expected and actual outputs have to consist of single tokens. No attempt is made, e.g., to accept [True, False] when a test expects [1, 0]. This is a simple hack for simple tests, and I intend to keep it that way.
* 2.3b2 on Windows will ship with Tcl/Tk 8.4.3. Note: this still didn'tTim Peters2003-06-221-0/+2
| | | | | | | fix the hangs on Win98SE when starting IDLE via "python" from a DOS box, but did appear to make them harder to provoke. I closed that bug report as being hopeless (and if someone wants to open it again, don't dare assign it to me again <0.1 wink>).
* Remove short-circuitying grubbing by using last grubbed buffer. It'sKen Manheimer2003-06-171-9/+5
| | | | | | | | | evil - if the last grubbed buffer didn't happen to be the right one, you couldn't remedy. Mainline emacs compat - don't use third arg to buffer-substring (which was for explicitly identifying the buffer in which to seek the substring, and which turns out to be unnecessary).
* SF Patch 569574 - enhancements to cgitb for plain text displaySkip Montanaro2003-06-171-0/+3
|
* SF #754014: list.index() should accept optional start, end argumentsRaymond Hettinger2003-06-171-0/+3
| | | | Also, modified UserList.index() to match and expanded the related tests.
* Add item about new threading module functions.Jeremy Hylton2003-06-161-0/+5
|
* Added two mac items (pimp auto-update and OSA property access).Jack Jansen2003-06-161-0/+3
|
* mimetools.choose_boundary() news.Tim Peters2003-06-151-0/+4
|
* Support keyword and topics help in cli(). Fixes #715782.Martin v. Löwis2003-06-141-0/+2
|
* Copy builtin functions as atomic. Fixes #746304. Will backport to 2.2.Martin v. Löwis2003-06-141-0/+1
|
* dummy_thread modified to have interrupt_main and to behave appropriately whenBrett Cannon2003-06-131-0/+3
| | | | | | | called. Added announcement in Misc/NEWS for thread.interrupt_main and mention of dummy_thread's change.
* News about the new IDLE (is more needed?). News about SF patchGuido van Rossum2003-06-131-0/+9
| | | | 751998.
* SF patch 707900, fixing bug 702858, by Steven Taschuk.Guido van Rossum2003-06-131-0/+4
| | | | | Copying a new-style class that had a reference to itself didn't work. (The same thing worked fine for old-style classes.)
* Warn about creating global variables by __setattr__ that shadow builtinNeil Schemenauer2003-06-091-0/+6
| | | | | names. Unfortunately, this is not bulletproof since the module dictionary can be modified directly.
* Add the IDLEFORK team.Raymond Hettinger2003-06-091-0/+2
|
* Added a command line interface for difflib.pyRaymond Hettinger2003-06-081-0/+3
|
* Announce difflib.context_diff() and difflib.unified_diff().Raymond Hettinger2003-06-081-0/+2
|
* The fix to use . was incorporatedNeal Norwitz2003-06-081-2/+1
|
* - urllib2.py now knows how to order proxy classes, so the user doesn'tGustavo Niemeyer2003-06-071-0/+5
| | | | | | have to insert it in front of other classes, nor do dirty tricks like inserting a "dummy" HTTPHandler after a ProxyHandler when building an opener with proxy support.
* Remove -U from argument list.Martin v. Löwis2003-05-261-3/+0
|
* Fleshed out WeakKeyDictionary.__delitem__ NEWS to cover issues raised onTim Peters2003-05-251-5/+13
| | | | | | | | | Python-Dev. Fixed typos in test comments. Added some trivial new test guts to show the parallelism (now) among __delitem__, __setitem__ and __getitem__ wrt error conditions. Still a bugfix candidate for 2.2.3 final, but waiting for Fred to get a chance to chime in.
* SF 742860: WeakKeyDictionary __delitem__ uses iterkeysTim Peters2003-05-251-0/+6
| | | | | | | | | | | | | | | | | Someone review this, please! Final releases are getting close, Fred (the weakref guy) won't be around until Tuesday, and the pre-patch code can indeed raise spurious RuntimeErrors in the presence of threads or mutating comparison functions. See the bug report for my confusions: I can't see any reason for why __delitem__ iterated over the keys. The new one-liner implementation is much faster, can't raise RuntimeError, and should be better-behaved in all respects wrt threads. New tests test_weak_keyed_bad_delitem and test_weak_keyed_cascading_deletes fail before this patch. Bugfix candidate for 2.2.3 too, if someone else agrees with this patch.
* SF bug 705231: Assertion failed, python aborts.Tim Peters2003-05-241-0/+6
| | | | | | | float_pow(): Don't let the platform pow() raise -1.0 to an integer power anymore; at least glibc gets it wrong in some cases. Note that math.pow() will continue to deliver wrong (but platform-native) results in such cases.
* PyType_Ready(): Complain if the type is a base type, and gc'able, andTim Peters2003-05-211-0/+11
| | | | | | | | | | | | | | | | | | tp_free is NULL or PyObject_Del at the end. Because it's a base type it must call tp_free in its dealloc function, and because it's gc'able it must not call PyObject_Del. inherit_slots(): Don't inherit tp_free unless the type and its base agree about whether they're gc'able. If the type is gc'able and the base is not, and the base uses the default PyObject_Del for its tp_free, give the type PyObject_GC_Del for its tp_free (the appropriate default for a gc'able type). cPickle.c: The Pickler and Unpickler types claim to be base classes and gc'able, but their dealloc functions didn't call tp_free. Repaired that. Also call PyType_Ready() on these typeobjects, so that the correct (PyObject_GC_Del) default memory-freeing function gets plugged into these types' tp_free slots.