summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fold long lines. (Walter, please take note! :-)Guido van Rossum2002-04-131-9/+18
|
* Add pop() to UserDict.Guido van Rossum2002-04-131-0/+2
|
* _PyObject_DebugDumpStats: renamed to _PyObject_DebugMallocStats.Tim Peters2002-04-133-5/+14
| | | | | | Added code to call this when PYMALLOC_DEBUG is enabled, and envar PYTHONMALLOCSTATS is set, whenever a new arena is obtained and once late in the Python shutdown process.
* SF bug 543148: Memory leak with stackframes + inspect.Tim Peters2002-04-131-2/+17
| | | | | | | | Put a bound on the number of frameobjects that can live in the frameobject free_list. Am also backporting to 2.2. I don't intend to backport to 2.1 (too much work -- lots of cyclic structures leak there, and the GC API).
* Document the optional argument to the .strip(), .rstrip(), .strip() stringFred Drake2002-04-131-8/+20
| | | | | methods. Part of SF feature #444708.
* News for strip methods.Guido van Rossum2002-04-131-0/+4
|
* Partially implement SF feature request 444708.Guido van Rossum2002-04-133-18/+101
| | | | | | | | | | | | | Add optional arg to string methods strip(), lstrip(), rstrip(). The optional arg specifies characters to delete. Also for UserString. Still to do: - Misc/NEWS - LaTeX docs (I did the docstrings though) - Unicode methods, and Unicode support in the string methods.
* Add news about memory managent APIs changing.Neil Schemenauer2002-04-121-0/+5
|
* Additional support for describing C structure members.Fred Drake2002-04-121-0/+11
|
* Integrate a bunch of new text from Guido.Fred Drake2002-04-121-6/+262
|
* AddrlistClass -> AddressListBarry Warsaw2002-04-121-2/+2
|
* AddrlistClass -> AddressListBarry Warsaw2002-04-121-2/+2
|
* Small anal correctness tweaks:Tim Peters2002-04-121-2/+2
| | | | | | | | | | _PyObject_DebugMalloc: explicitly cast PyObject_Malloc's result to the target pointer type. _PyObject_DebugDumpStats: change decl of arena_alignment from unsigned int to unsigned long. This is for the 2.3 release only (it's new code).
* BDFL agreed with Tim: rehabilitate randint().Fred Drake2002-04-121-1/+0
|
* Update the type of the tp_free slot.Fred Drake2002-04-121-1/+1
|
* Warn people away from PyModule_GetDict(), but not too strongly.Fred Drake2002-04-121-0/+3
| | | | | | | (The real issue is whether modules can benefit from an alternate implementation strategy rather than using a dictionary. We should migrate away from direct dictionary manipulation to allow more room for Jeremy to flex the implementation with changes in globals lookup.)
* News about dict.pop().Guido van Rossum2002-04-121-0/+3
|
* Do not use PyModule_GetDict().Fred Drake2002-04-121-23/+27
| | | | | Clean up the example of exporting a C-callable API from an extension module. Add a hyperlink to a related section in the Python/C API reference.
* Change example of retrieving & calling a Python function to not useFred Drake2002-04-121-12/+9
| | | | | PyModule_GetDict(), which is also more flexible: it does not assume that the "module" is a real module.
* Change the type of the tp_dealloc back to what it really is.Fred Drake2002-04-121-2/+2
| | | | Change a section title to fit in better.
* Bump AC_PREREQ to 2.53.Martin v. Löwis2002-04-122-2/+2
|
* I am mad. This test never worked!Guido van Rossum2002-04-121-16/+14
| | | | | | | | | | | | | | | | | | | | | | The test function's signature should be test(methodname, input, output, *args) but the output argument was omitted. This caused all tests to fail, because the expected output was passed as the initial argument to the method call. But because of the way the test works (it compares the results for a regular string to the results for a UserString instance with the same value, and it's OK if both raise the same exception) the test never failed! I've fixed this, and also cleaned up a few warts in the verbose output. Finally, I've made it possible to run the test stand-alone in verbose mode by passing -v as a command line argument. Now, the test will report failure related to zfill. That's not my fault, that's a legitimate problem: the string_tests.py file contains a test for the zfill() method (just added) but this method is not implemented. The responsible party will surely fix this soon now.
* Modernize the minimal example of an extension type.Fred Drake2002-04-121-7/+15
|
* Add a (very) simple description of PyType_Ready().Fred Drake2002-04-121-0/+4
|
* Update the type of tp_dealloc.Fred Drake2002-04-121-1/+1
|
* Spell Raymond Hettinger's name writeNeal Norwitz2002-04-121-1/+1
|
* Add Raymond Hettinger, CPA.Guido van Rossum2002-04-121-0/+1
|
* Add Raymond Hettinger's d.pop(). See SF patch 539949.Guido van Rossum2002-04-123-0/+56
|
* - Added support for inherent pointer types (typedefs of arrays)Jack Jansen2002-04-121-0/+34
| | | | - Added a debug class variable to enable parser debugging.
* Give type name when complaining about using input-only type for outputJack Jansen2002-04-121-2/+2
| | | | or v.v.
* Remove acconfig.h.Martin v. Löwis2002-04-124-41/+10
|
* Remove unused macros.Martin v. Löwis2002-04-121-23/+0
|
* Update to autoconf 2.5x.Martin v. Löwis2002-04-124-4824/+13539
|
* _PyObject_DebugRealloc(): rewritten to let the underlying realloc doTim Peters2002-04-121-27/+30
| | | | | | | | | | most of the work. In particular, if the underlying realloc is able to grow the memory block in place, great (this routine used to do a fresh malloc + memcpy every time a block grew). BTW, I'm not so keen here on avoiding possible quadratic-time realloc patterns as I am on making the debug pymalloc more invisible (the more it uses memory "just like" the underlying allocator, the better the chance that a suspected memory corruption bug won't vanish when the debug malloc is turned on).
* _PyObject_DebugDumpAddress(): clarify an output message.Tim Peters2002-04-121-1/+1
|
* PYMALLOC_{CLEAN, DEAD, FORBIDDEN}BYTE symbols: remove the PYMALLOC_Tim Peters2002-04-121-34/+39
| | | | | prefix. These symbols are private to the file, and the PYMALLOC_ gets in the way (overly long code lines, comments, and error messages).
* First stab at rationalizing the PyMem_ API. Mixing PyObject_xyz withTim Peters2002-04-124-70/+61
| | | | | | | | | | | | | | | | | | | | | | | | PyMem_{Del, DEL} doesn't work yet (compilation problems). pyport.h: _PyMem_EXTRA is gone. pmem.h: Repaired comments. PyMem_{Malloc, MALLOC} and PyMem_{Realloc, REALLOC} now make the same x-platform guarantees when asking for 0 bytes, and when passing a NULL pointer to the latter. object.c: PyMem_{Malloc, Realloc} just call their macro versions now, since the latter take care of the x-platform 0 and NULL stuff by themselves now. pypcre.c, grow_stack(): So sue me. On two lines, this called PyMem_RESIZE to grow a "const" area. It's not legit to realloc a const area, so the compiler warned given the new expansion of PyMem_RESIZE. It would have gotten the same warning before if it had used PyMem_Resize() instead; the older macro version, but not the function version, silently cast away the constness. IMO that was a wrong thing to do, and the docs say the macro versions of PyMem_xyz are deprecated anyway. If somebody else is resizing const areas with the macro spelling, they'll get a warning when they recompile now too.
* First cut at repairing out-of-date comments; make alignment of macro defsTim Peters2002-04-121-15/+24
| | | | all the same within the #ifdef WITH_PYMALLOC block.
* Move PyObject_Malloc and PyObject_Free here from object.c. RemoveNeil Schemenauer2002-04-121-61/+33
| | | | | PyMalloc_ prefix and use PyObject_ instead. I'm not sure about the debugging functions. Perhaps they should stay as PyMalloc_.
* Move PyObject_Malloc and PyObject_Free to obmalloc.c.Neil Schemenauer2002-04-121-21/+2
|
* Remove PyMalloc_*.Neil Schemenauer2002-04-121-5/+5
|
* Change signature of _PyObject_GC_Malloc to match PyObject_MALLOC.Neil Schemenauer2002-04-121-6/+6
| | | | | PyObject_Del and PyObject_GC_Del can now be used as a function designators.
* PyObject_GC_Del can now be used as a function designator.Neil Schemenauer2002-04-121-1/+1
|
* Remove PyMalloc_New and PyMalloc_Del.Neil Schemenauer2002-04-122-4/+4
|
* Remove PyMalloc_New, _PyMalloc_MALLOC, and PyMalloc_Del.Neil Schemenauer2002-04-121-7/+7
|
* Remove PyMalloc_New and PyMalloc_Del.Neil Schemenauer2002-04-121-2/+2
|
* PyObject_GC_Del can now be used as a function designator.Neil Schemenauer2002-04-123-3/+3
|
* PyObject_Del can now be used as a function designator.Neil Schemenauer2002-04-126-7/+7
|
* PyObject_GC_Del and PyObject_Del can now be used as a functionNeil Schemenauer2002-04-121-3/+3
| | | | | | designators. Remove PyMalloc_New.
* Allow PyObject_Del to be used as a function designator. Provide binaryNeil Schemenauer2002-04-121-14/+39
| | | | | | | | compatibility function. Make PyObject_GC_Track and PyObject_GC_UnTrack functions instead of trivial macros wrapping functions. Provide binary compatibility functions.
generated by cgit v0.12 at 2024-12-01 06:15:51 (GMT)