summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Guido suggests, and I agree, to insist that SIZEOF_VOID_P be a power of 2.Tim Peters2001-10-074-48/+32
| | | | | | This simplifies the rounding in _PyObject_VAR_SIZE, allows to restore the pre-rounding calling sequence, and allows some nice little simplifications in its callers. I'm still making it return a size_t, though.
* Remove code and docs for the OldProfile and HotProfile classes: codeTim Peters2001-10-073-285/+32
| | | | | hasn't worked in years, docs were wrong, and they aren't interesting anymore regardless.
* _PyObject_VAR_SIZE: always round up to a multiple-of-pointer-size value.Tim Peters2001-10-064-61/+70
| | | | | | | | | | | | | | | | | As Guido suggested, this makes the new subclassing code substantially simpler. But the mechanics of doing it w/ C macro semantics are a mess, and _PyObject_VAR_SIZE has a new calling sequence now. Question: The PyObject_NEW_VAR macro appears to be part of the public API. Regardless of what it expands to, the notion that it has to round up the memory it allocates is new, and extensions containing the old PyObject_NEW_VAR macro expansion (which was embedded in the PyObject_NEW_VAR expansion) won't do this rounding. But the rounding isn't actually *needed* except for new-style instances with dict pointers after a variable-length blob of embedded data. So my guess is that we do not need to bump the API version for this (as the rounding isn't needed for anything an extension can do unless it's recompiled anyway). What's your guess?
* Repaired the debug Windows deaths in test_descr, by allocating enoughTim Peters2001-10-063-21/+33
| | | | | | | | | | | | | | pad memory to properly align the __dict__ pointer in all cases. gcmodule.c/objimpl.h, _PyObject_GC_Malloc: + Added a "padding" argument so that this flavor of malloc can allocate enough bytes for alignment padding (it can't know this is needed, but its callers do). typeobject.c, PyType_GenericAlloc: + Allocated enough bytes to align the __dict__ pointer. + Sped and simplified the round-up-to-PTRSIZE logic. + Added blank lines so I could parse the if/else blocks <0.7 wink>.
* _PyObject_GetDictPtr():Tim Peters2001-10-061-8/+12
| | | | | | + Use the _PyObject_VAR_SIZE macro to compute object size. + Break the computation into lines convenient for debugger inspection. + Speed the round-up-to-pointer-size computation.
* _PyObject_GC_Malloc(): split a complicated line in two. As is, there wasTim Peters2001-10-061-2/+3
| | | | | no way to talk the debugger into showing me how many bytes were being allocated.
* Update the documentation to reflect the changes to ReferenceError.Fred Drake2001-10-062-1/+13
|
* The fix to profile semantics broke the miserable but advertised way toTim Peters2001-10-051-25/+26
| | | | | derive Profile subclasses. This patch repairs that, restoring negative tuple indices. Yuck? You bet.
* Teach Windows how to build the new weakref module.Tim Peters2001-10-051-0/+15
|
* Remove bogus declaration.Fred Drake2001-10-051-2/+0
|
* Add documentation for the public API for weak reference objects.Fred Drake2001-10-051-1/+70
|
* Adjust the _weakref module to use the public API for the weak referenceFred Drake2001-10-051-717/+15
| | | | | objects. This is now simply a shim to give weakref.py access to the underlying implementation.
* PyObject_ClearWeakRefs() is now a real function instead of a function pointer;Fred Drake2001-10-052-16/+1
| | | | the implementation is in Objects/weakrefobject.c.
* Add dependencies for the weakref object.Fred Drake2001-10-051-0/+2
|
* Include the weakref object interface.Fred Drake2001-10-051-0/+1
|
* ReferenceError is now built-in, so pick it up from the right place.Fred Drake2001-10-051-1/+3
| | | | It still needs to be here to preserve the API.
* The weak reference implementation, separated from the weakref module.Fred Drake2001-10-052-0/+765
|
* weakref.ReferenceError becomes a built-in exception now that weak ref objectsFred Drake2001-10-052-0/+7
| | | | | are moving into the core; with these changes, it will be possible for the exception to be raised without the weakref module ever being imported.
* Martijn Pieters convinced me that when readline() strips the trailingGuido van Rossum2001-10-051-2/+5
| | | | newline from a multifile part, it should also strip a trailing \r\n.
* Enable GC for new-style instances. This touches lots of files, sinceGuido van Rossum2001-10-0513-26/+90
| | | | | | | | | | | | | | | | | | | | | | many types were subclassable but had a xxx_dealloc function that called PyObject_DEL(self) directly instead of deferring to self->ob_type->tp_free(self). It is permissible to set tp_free in the type object directly to _PyObject_Del, for non-GC types, or to _PyObject_GC_Del, for GC types. Still, PyObject_DEL was a tad faster, so I'm fearing that our pystone rating is going down again. I'm not sure if doing something like void xxx_dealloc(PyObject *self) { if (PyXxxCheckExact(self)) PyObject_DEL(self); else self->ob_type->tp_free(self); } is any faster than always calling the else branch, so I haven't attempted that -- however those types whose own dealloc is fancier (int, float, unicode) do use this pattern.
* With Andrew's blessing: distutils version number is now 1.0.3.Thomas Heller2001-10-051-1/+1
|
* Introduced the oddly-missing PyList_CheckExact(), and used it to replaceTim Peters2001-10-052-1/+2
| | | | a hard-coded type check.
* Explicitely list the metadata attributes to showThomas Heller2001-10-051-295/+304
| | | | | in the gui. Updated to include the new exe-file.
* Get rid of unique local ISSTRICTINT macro in favor of std PyInt_CheckExact.Tim Peters2001-10-051-9/+6
|
* A regexp example was rendered asTim Peters2001-10-051-1/+1
| | | | | | | | | | foo\d when it was clearly intended to render as foo$ Fred, is this a right way to fix it? If not, the earlier place in the same paragraph that does render as foo$ is also wrong.
* SMTPServer.__init__(): Print the start information on the DEBUGSTREAMBarry Warsaw2001-10-051-1/+2
| | | | so that it can be suppressed.
* Remove false statement about running make in the Modules directory.Guido van Rossum2001-10-051-3/+2
|
* Remove some long-unsupported Mac OS modules.Fred Drake2001-10-055-425/+0
| | | | This closes SF patch #460737.
* Frankly, I'd like my "L." as well!Fred Drake2001-10-051-1/+1
|
* Another contributor.Guido van Rossum2001-10-051-1/+2
| | | | Give Fred his Jr.
* Fix typo in docstringAndrew M. Kuchling2001-10-051-1/+1
|
* Document addition of chroot.Martin v. Löwis2001-10-041-0/+2
|
* Add chroot call. Implements feature #459267.Martin v. Löwis2001-10-045-3/+27
|
* Update a couple of old addresses that point to CNRI.Fred Drake2001-10-042-9/+11
|
* Non-failing test for SF bug #467059.Fred Drake2001-10-041-0/+42
|
* Apply modified SF patch 467580: ConfigParser.getboolean(): FALSE, TRUE.Guido van Rossum2001-10-041-6/+8
| | | | | | | | | | | | | | This patch allows ConfigParser.getboolean() to interpret TRUE, FALSE, YES, NO, ON and OFF instead just '0' and '1'. While just allowing '0' and '1' sounds more correct users often demand to use more descriptive directives in configuration files. Instead of forcing every programmer do brew his own solution a system should include the batteries for this. [My modification to the patch is a slight rewording of the docstring and use of lowercase instead of uppercase templates. The code is still case sensitive. GvR.]
* run_suite(): If testclass is not available, provide an even more generalFred Drake2001-10-041-4/+8
| | | | | | | error message. run_unittest(): Provide the testclass to run_suite() so it can construct the error message. This closes SF bug #467763.
* Make new classes dynamic by default.Guido van Rossum2001-10-043-26/+24
|
* Changed the reindenter to strip only trailing spaces and tabs from lines,Tim Peters2001-10-041-3/+16
| | | | | not other control characters string.rstrip() got rid of. This caters to the \f thingies Barry likes putting in Python source files.
* Fix bug in profiler modifications detected only in debug builds.Fred Drake2001-10-041-3/+26
| | | | | | | | | The new profiler event stream includes a "return" event even when an exception is being propogated, but the machinery that called the profile hook did not save & restore the exception. In debug mode, the exception was detected during the execution of the profile callback, which did not have the proper internal flags set for the exception. Saving & restoring the exception state solves the problem.
* TestIterators: Tim Peters suggests a more succinct spelling ofBarry Warsaw2001-10-041-12/+4
| | | | "listify an iterator".
* More test data for test_email.pyBarry Warsaw2001-10-042-0/+49
|
* test_header_splitter(), test_body_line_iterator(): Move the test dataBarry Warsaw2001-10-041-70/+32
| | | | into tests/data/msg_*.txt files.
* Give me back my page breaks.Barry Warsaw2001-10-0412-22/+22
|
* Add note about profiling.Guido van Rossum2001-10-041-0/+15
|
* Script arguments localhost:localport and remotehost:remoteport are nowBarry Warsaw2001-10-041-18/+28
| | | | | | | | | | | | | optional, and default to `localhost' and ports 8025 and 25 respectively. SMTPChannel.__init__(): Calculate __fqdn using socket.getfqdn() instead of gethostby*() and friends. This allows us to run this script even if we don't have access to dns (assuming the localhost is configured properly). Also, restore my precious page breaks. Hands off, oh Whitespace Normalizer!
* Add various typecasts (back and forth from char * to unsigned char *)Greg Ward2001-10-041-5/+5
| | | | to make the SGI C compiler happier (bug #445960).
* Remove a couple of unused local variables (bug #445960, compiler warningsGreg Ward2001-10-041-4/+2
| | | | on IRIX 6.5).
* Updated to reflect the rationalized profiler event reporting.Fred Drake2001-10-041-46/+27
|
* Rationalize the events passed to the profiler (no changes for the tracer).Fred Drake2001-10-042-10/+6
| | | | | | | | | | | | | | | | | | | | | | | | The profiler does not need to know anything about the exception state, so we no longer call it when an exception is raised. We do, however, make sure we *always* call the profiler when we exit a frame. This ensures that timing events are more easily isolated by a profiler and finally clauses that do a lot of work don't have their time mis-allocated. When an exception is propogated out of the frame, the C callback for the profiler now receives a PyTrace_RETURN event with an arg of NULL; the Python-level profile hook function will see a 'return' event with an arg of None. This means that from Python it is impossible for the profiler to determine if the frame exited with an exception or if it returned None, but this doesn't matter for profiling. A C-based profiler could tell the difference, but this doesn't seem important. ceval.c:eval_frame(): Simplify the code in two places so that the profiler is called for every exit from a frame and not for exceptions. sysmodule.c:profile_trampoline(): Make sure we don't expose Python code to NULL; use None instead.
generated by cgit v0.12 at 2025-02-27 11:04:21 (GMT)