summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Work around limitation of Cygwin Perl: To avoid a permission denial, we needFred Drake2002-05-021-1/+10
| | | | | | to do the inplace-edit with a backup file. A quick test leads me to believe this is sufficient to allow building the documentation on Cygwin; a full test is in progress.
* Indicate delayed initialization of slots. Suggested by tim.one.Martin v. Löwis2002-05-021-3/+5
|
* Patch #551008: DL_IMPORT PyBool_FromLong.Martin v. Löwis2002-05-021-1/+1
|
* PyObject_Realloc(): If a small block is shrinking, bite the expense ofTim Peters2002-05-021-5/+16
| | | | copying it if at least 25% of the input block can be reclaimed.
* Patch #551009: Initialize array type dynamically.Martin v. Löwis2002-05-021-3/+6
|
* Remove old deprecated features from the xrange object.Fred Drake2002-05-021-273/+40
|
* Remove all tests that rely on deprecated-in-2.2 features of xrange objects.Fred Drake2002-05-022-29/+0
| | | | | "What's New in Python 2.2" documented that these would be removed in Python 2.3.
* Many minor markup adjustments for consistency.Fred Drake2002-05-021-10/+10
|
* Remove extra period produced by previous change.Fred Drake2002-05-021-3/+3
|
* Patch 550804: Make os.environ.copy() return a copy.Martin v. Löwis2002-05-021-0/+4
|
* Added regression tests for xrange object attributes.Fred Drake2002-05-021-0/+23
| | | | See SF bug #551285.
* Fix attribute access for the xrange objects. The tp_getattr and tp_getattroFred Drake2002-05-021-31/+38
| | | | | | handlers were both set, but were not compatible. This change uses only the tp_getattro handler with a more "modern" approach. This fixes SF bug #551285.
* Correct Moshe's e-mail addressAndrew M. Kuchling2002-05-021-8/+6
| | | | | | Point to PEP 100 for MAL's Unicode proposal Fix URL for XML HOWTO Bump version number
* Note that NameError's message also changed in 2.0Andrew M. Kuchling2002-05-021-8/+10
|
* Message for NameError has changedAndrew M. Kuchling2002-05-021-1/+1
|
* clarify message when raising TypeError to indicate that float() acceptsSkip Montanaro2002-05-021-1/+1
| | | | strings or numbers
* Guard gettext and friends with HAVE_LIBINTL_H. Fixes #549907.Martin v. Löwis2002-05-021-1/+1
|
* Correct information on support for repietition & concatenation for bufferFred Drake2002-05-021-6/+8
| | | | | and xrange objects. This closes SF bug #550555.
* Buffer-object repitition and concatenation has worked all along; add a testFred Drake2002-05-021-0/+6
| | | | to make avoid regression.
* Added some notes on setting up the documentation tools on Cygwin.Fred Drake2002-05-011-0/+40
|
* Added more style for major warnings.Fred Drake2002-05-011-0/+9
|
* Pickler_clear_memo(): convert to METH_NOARGS.Fred Drake2002-05-011-5/+2
|
* Add Pickler.clear_memo() so the pickle and cPickle modules are more similar.Fred Drake2002-05-013-4/+15
|
* list_documented_items(): Basic implementation.Fred Drake2002-05-011-4/+33
| | | | | This still does not work well since ctags does not do a good job with the Python headers, appearantly due to the DL_IMPORT macro. ;-(
* Explain what os.read() returns at end of file.Fred Drake2002-05-011-1/+3
| | | | This closes SF bug #550409. Applying to release21-maint & release22-maint.
* Add missing right-parenthesis.Fred Drake2002-05-011-1/+1
|
* Watch out for older XEmacsen for which requiring info-look doesn'tBarry Warsaw2002-04-301-8/+11
| | | | define info-lookup-maybe-add-help.
* moved from Tools/scripts (was only at rev 1.1 - no changes yet - so I simplySkip Montanaro2002-04-301-0/+128
| | | | removed it from there and added it here)
* moving into the Doc/tools directorySkip Montanaro2002-04-301-128/+0
|
* Add a note about when the "%r" formatting code was added.Fred Drake2002-04-301-0/+1
|
* add enumobject.c to build machineryAndrew MacIntyre2002-04-301-2/+3
|
* Fred's recent changes to support "-u all" resulted in subset resourceAndrew MacIntyre2002-04-301-1/+1
| | | | selections (eg "-u network") being ignored.
* add enumobject.c to build machineryAndrew MacIntyre2002-04-301-0/+4
|
* Added a missing "|" in the grammar productions used in the reference manualFred Drake2002-04-301-7/+9
| | | | | | | (reported by François Pinard). Added some missing "_" characters in the same cluster of productions. Added missing floor division operator in m_expr production, and mention floor division in the relevant portion of the text.
* builtin_zip(): Take a good guess at how big the result list will be,Tim Peters2002-04-292-15/+70
| | | | | | | and allocate it in one gulp. This isn't a bugfix, it's just a minor optimization that may or may not pay off.
* Typo: whcar_t should be wchar_t.Thomas Heller2002-04-291-4/+4
| | | | Bugfix candidate? Don't know how this is handled in the docs.
* Add some items, and remove a note to myselfAndrew M. Kuchling2002-04-291-7/+7
|
* Small markup adjustments for consistency.Fred Drake2002-04-291-2/+2
|
* See discussion at SF bug 547537.Guido van Rossum2002-04-291-1/+1
| | | | | | | | | | | Unicode objects are currently taken as binary data by the write() method. This is not what Unicode users expect, nor what the StringIO.py code does. Until somebody adds a way to specify binary or text mode for cStringIO objects, change the format string to use "t#" instead of "s#", so that it will request the "text buffer" version. This will try the default encoding for Unicode objects. This is *not* a 2.2 bugfix (since it *is* a semantic change).
* Mostly in SequenceMatcher.{__chain_b, find_longest_match}:Tim Peters2002-04-293-34/+84
| | | | | | | | | | | | This now does a dynamic analysis of which elements are so frequently repeated as to constitute noise. The primary benefit is an enormous speedup in find_longest_match, as the innermost loop can have factors of 100s less potential matches to worry about, in cases where the sequences have many duplicate elements. In effect, this zooms in on sequences of non-ubiquitous elements now. While I like what I've seen of the effects so far, I still consider this experimental. Please give it a try!
* Just added comments, and cleared some XXX questions, related to intTim Peters2002-04-281-3/+12
| | | | memory management.
* _PyObject_DebugCheckAddress(): If the leading pad bytes are corrupt,Tim Peters2002-04-281-18/+25
| | | | | display a msg warning that the count of bytes requested may be bogus, and that a segfault may happen next.
* Moving pymalloc along.Tim Peters2002-04-282-112/+131
| | | | | | | | | | As threatened, PyMem_{Free, FREE} also invoke the object deallocator now when pymalloc is enabled (well, it does when pymalloc isn't enabled too, but in that case "the object deallocator" is plain free()). This is maximally backward-compatible, but it leaves a bitter aftertaste. Also massive reworking of comments.
* _PyObject_GC_New: Could call PyObject_INIT with a NULL 1st argument.Tim Peters2002-04-281-2/+6
| | | | | | _PyObject_GC_NewVar: Could call PyObject_INIT_VAR likewise. Bugfix candidate.
* Repair widespread misuse of _PyString_Resize. Since it's clear peopleTim Peters2002-04-2714-90/+54
| | | | | | | | | | | | | | | | | | | | | | don't understand how this function works, also beefed up the docs. The most common usage error is of this form (often spread out across gotos): if (_PyString_Resize(&s, n) < 0) { Py_DECREF(s); s = NULL; goto outtahere; } The error is that if _PyString_Resize runs out of memory, it automatically decrefs the input string object s (which also deallocates it, since its refcount must be 1 upon entry), and sets s to NULL. So if the "if" branch ever triggers, it's an error to call Py_DECREF(s): s is already NULL! A correct way to write the above is the simpler (and intended) if (_PyString_Resize(&s, n) < 0) goto outtahere; Bugfix candidate.
* SF patch 549375: Compromise PyUnicode_EncodeUTF8Tim Peters2002-04-271-108/+70
| | | | | | | | | | | | | | | | | | | | This implements ideas from Marc-Andre, Martin, Guido and me on Python-Dev. "Short" Unicode strings are encoded into a "big enough" stack buffer, then exactly as much string space as they turn out to need is allocated at the end. This should have speed benefits akin to Martin's "measure once, allocate once" strategy, but without needing a distinct measuring pass. "Long" Unicode strings allocate as much heap space as they could possibly need (4 x # Unicode chars), and do a realloc at the end to return the untouched excess. Since the overallocation is likely to be substantial, this shouldn't burden the platform realloc with unusably small excess blocks. Also simplified uses of the PyString_xyz functions. Also added a release- build check that 4*size doesn't overflow a C int. Sooner or later, that's going to happen.
* Teach the Windows build about the new enumobject.c file.Tim Peters2002-04-261-0/+15
|
* Slightly expand and clarify the differences between getegid(), getgid(),Fred Drake2002-04-261-6/+9
| | | | | getpgrp(), and setpgid(). This closes SF bug #547939.
* Be more consistent, both internally and with recommended practice.Fred Drake2002-04-261-4/+2
| | | | This closes SF bug #547953.
* Documentation for the enumerate() function/type.Fred Drake2002-04-262-0/+55
| | | | This closes SF patch #547162.
generated by cgit v0.12 at 2025-09-24 06:22:00 (GMT)