summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add MessageBeep() API.Guido van Rossum2003-04-092-2/+23
|
* Detabified.Guido van Rossum2003-04-091-20/+5
| | | | Removed dead code.
* Make it possible to call instancemethod() with 2 arguments.Guido van Rossum2003-04-091-2/+2
|
* Reformat a few docstrings that caused line wraps in help() output.Guido van Rossum2003-04-092-12/+12
|
* Fix two crashes on Windows:Guido van Rossum2003-04-091-2/+2
| | | | | - CHECK_VALID() was checking the wrong value for a closed fd - fseek(&_iob[fileno], ...) doesn't work for fileno >= 20
* Various improvements to the way the table is formatted, to deal withGuido van Rossum2003-04-091-21/+36
| | | | exceptionally large totals etc.
* - New function sys.call_tracing() allows pdb to debug codeGuido van Rossum2003-04-095-0/+78
| | | | | | recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
* Minor markup adjustments.Fred Drake2003-04-091-3/+2
|
* Try to discourage use of PyObject_Type().Guido van Rossum2003-04-091-0/+5
|
* Don't use (PyObject *)PyObject_Type(x). It is a leaky and verbose wayGuido van Rossum2003-04-091-2/+2
| | | | of saying x->ob_type.
* Re-indent example; fix typoAndrew M. Kuchling2003-04-091-4/+4
|
* property_traverse() should also traverse into prop_doc -- there's noGuido van Rossum2003-04-091-0/+1
| | | | | typecheck that guarantees it's a string, and BTW string subclasses could hide references.
* Patch #709178: remove -static option from cygwinccompilerJason Tishler2003-04-091-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, the cygwinccompiler.py compiler handling in distutils is invoking the cygwin and mingw compilers with the -static option. Logically, this means that the linker should choose to link to static libraries instead of shared/dynamically linked libraries. Current win32 binutils expect import libraries to have a .dll.a suffix and static libraries to have .a suffix. If -static is passed, it will skip the .dll.a libraries. This is pain if one has a tree with both static and dynamic libraries using this naming convention, and wish to use the dynamic libraries. The -static option being passed in distutils is to get around a bug in old versions of binutils where it would get confused when it found the DLLs themselves. The decision to use static or shared libraries is site or package specific, and should be left to the setup script or to command line options.
* Created a minimal MacOSX section.Jack Jansen2003-04-091-92/+176
|
* Detabbed.Jack Jansen2003-04-0923-7956/+7970
|
* Remove the --verify option in favor of the standard -n/--dry-run optionAndrew M. Kuchling2003-04-091-4/+1
|
* Lots of small markup adjustments.Fred Drake2003-04-092-113/+118
|
* Add dependency information for the hotshot package docs.Fred Drake2003-04-091-0/+1
|
* extra punctuation removedAnthony Baxter2003-04-091-1/+1
|
* Add dependency information for the timeit module docs.Fred Drake2003-04-091-0/+1
|
* + libtimeitSkip Montanaro2003-04-091-0/+1
|
* doc for timeit module/script - mostly just a recast of Tim's docstringSkip Montanaro2003-04-091-0/+184
|
* Make staticmethods and classmethods participate in GC.Jeremy Hylton2003-04-081-8/+45
| | | | | | | | | | If a class was defined inside a function, used a static or class method, and used super() inside the method body, it would be caught in an uncollectable cycle. (Simplified version: The static/class method object would point to a function object with a closure that referred to the class.) Bugfix candidate.
* tentative fix for #712322: modification time stamp checking failedJust van Rossum2003-04-081-1/+1
| | | | when DST began.
* install timeit.py as a command line scriptSkip Montanaro2003-04-081-0/+1
|
* add a #! line for unix weeniesSkip Montanaro2003-04-081-0/+2
|
* New tests identical to boom and boom2, except using new-style classes.Tim Peters2003-04-081-0/+44
| | | | | | | These never failed in 2.3, and the tests confirm it. They still blow up in the 2.2 branch, despite that all the gc-vs-__del__ fixes from 2.3 have been backported (and this is expected -- 2.2 needs more work than 2.3 needed).
* correct a couple docstring nitsSkip Montanaro2003-04-081-3/+3
|
* Typo repair.Tim Peters2003-04-081-2/+2
|
* Added example of using positional and keyword args with atexit.register().Fred Drake2003-04-081-0/+15
| | | | Based on a suggestion from a reader.
* Markup fix.Fred Drake2003-04-081-2/+2
|
* s/referrents/referents/g. Gotta love that referrers remains rife with rs.Tim Peters2003-04-084-22/+22
|
* Finished implementing gc.get_referrents(): dealt with error and endTim Peters2003-04-084-7/+58
| | | | cases, wrote docs, added a test.
* Comment repair; no semantic changes.Tim Peters2003-04-071-4/+5
|
* Reworked has_finalizer() to use the new _PyObject_Lookup() insteadTim Peters2003-04-073-78/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
* New private API function _PyInstance_Lookup. gc will use this to figureTim Peters2003-04-072-0/+33
| | | | out whether __del__ exists, without executing any Python-level code.
* add note suggested by rhettinger about example.Anthony Baxter2003-04-071-0/+3
|
* patch [ 698505 ] docs for hotshot moduleAnthony Baxter2003-04-072-0/+124
|
* initgc(): Rewrote to use the PyModule_AddXYZ API; cuts code size.Tim Peters2003-04-061-17/+14
|
* handle_finalizers(): Rewrote to call append_objects() and gc_list_merge()Tim Peters2003-04-061-36/+31
| | | | | | | | | instead of looping. Smaller and clearer. Faster, too, when we're not appending to gc.garbage: gc_list_merge() takes constant time, regardless of the lists' sizes. append_objects(): Moved up to live with the other list manipulation utilities.
* SF bug #699934: Obscure error messageRaymond Hettinger2003-04-062-7/+4
| | | | | mwh pointed out that the error message did not make sense if obtained by rearranging the bases.
* SF patch #701494: more apply removalsRaymond Hettinger2003-04-0623-2472/+2460
|
* Switched from METH_VARARGS to METH_NOARGS for the 7 module functions thatTim Peters2003-04-061-44/+17
| | | | take no arguments; cuts generated code size.
* Reworked move_finalizer_reachable() to create two distinct lists:Tim Peters2003-04-062-35/+89
| | | | | | | | | externally unreachable objects with finalizers, and externally unreachable objects without finalizers reachable from such objects. This allows us to call has_finalizer() at most once per object, and so limit the pain of nasty getattr hooks. This fixes the failing "boom 2" example Jeremy posted (a non-printing variant of which is now part of test_gc), via never triggering the nasty part of its __getattr__ method.
* move_finalizers(): Rewrote. It's not necessary for this routineTim Peters2003-04-051-29/+20
| | | | | | | | | | | | | | to special-case classic classes, or to worry about refcounts; has_finalizer() deleted the current object iff the first entry in the unreachable list has changed. I don't believe it was correct to check for ob_refcnt == 1, either: the dealloc routine would get called by Py_DECREF then, but there's nothing to stop the dealloc routine from ressurecting the object, and then gc would remain at the head of the unreachable list despite that its refcount temporarily fell to 0 (and that would lead to an infinite loop in move_finalizers()). I'm still worried about has_finalizer() resurrecting other objects in the unreachable list: what's to stop them from getting collected?
* test_boom: More comments. Also check that len(gc.garbage) doesn'tTim Peters2003-04-051-4/+9
| | | | | change (it would be another kind of bug if the trash cycle weren't reclaimed).
* New comments. Rewrote has_finalizer() as a sequence of ifs instead ofTim Peters2003-04-051-6/+21
| | | | | | squashed-together conditional operators; makes it much easier to step thru in the debugger, and to set a breakpoint on the only dangerous path.
* Fixed new seemingly random segfaults, by moving the initialization ofTim Peters2003-04-051-8/+11
| | | | | | | | | | delstr from initgc() into collect(). initgc() isn't called unless the user explicitly imports gc, so can be used only for initialization of user-visible module features; delstr needs to be initialized for proper internal operation, whether or not gc is explicitly imported. Bugfix candidate? I don't know whether the new bug was backported to 2.2 already.
* SF bug #715145: unittest.py still uses != in failUnlessEqualRaymond Hettinger2003-04-042-2/+6
|
* Add Tim's gc boom test to the test suite.Jeremy Hylton2003-04-041-0/+19
|
generated by cgit v0.12 at 2024-12-03 10:21:58 (GMT)