summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* - general markup cleanupFred Drake2003-12-311-21/+19
| | | | | - rearrange so two small sections become one; this avoids an extra page in the HTML format
* general markup improvementsFred Drake2003-12-311-5/+6
|
* - add link to the datetime moduleFred Drake2003-12-311-0/+1
|
* - update description of isleap()Fred Drake2003-12-311-1/+5
| | | | - add link to the datetime module
* - use the same markup for the deprecation as for that ofFred Drake2003-12-311-1/+1
| | | | file.xreadlines()
* - add a "See also" reference to the doctest moduleFred Drake2003-12-311-24/+25
| | | | | - slightly simplify a couple of examples - clean up some markup
* Strengthen the test for hash effectivenessRaymond Hettinger2003-12-311-4/+4
|
* Various fixups:Raymond Hettinger2003-12-311-26/+36
| | | | | | | | * Add comment on the future of the sets module. * Change a variable from "input" to "data" to avoid shadowing a builtin. * Added possible applications for str.rsplit() and itertools.tee(). * Repaired the example for sorted(). * Cleaned-up the example for operator.itemgetter().
* fix truly evil markup typoFred Drake2003-12-301-1/+1
|
* minor cleanup of exampleFred Drake2003-12-301-4/+6
|
* - we *really* don't care about Python 1.5 alphas any more!Fred Drake2003-12-301-6/+4
| | | | - note the interpreter's -S option
* fix a variety of markup bugsFred Drake2003-12-301-24/+24
|
* work around whitespace bugs in the HTML versionFred Drake2003-12-301-3/+3
|
* fix markup errorsFred Drake2003-12-301-3/+2
|
* lots of markup adjustmentsFred Drake2003-12-301-34/+43
|
* markup fixFred Drake2003-12-302-4/+5
|
* Fixes to support CJKCodecs as per SF bug #852347. Actually, thisBarry Warsaw2003-12-301-19/+16
| | | | | | | | | | | patch removes dependencies on the old unsupported KoreanCodecs package and the alternative JapaneseCodecs package. Since both of those provide aliases for their codecs, this removal just makes the generic codec names work. We needed to make slight changes to __init__() as well. This will be backported to Python 2.3 when its branch freeze is over.
* Bump version number to 2.5.5Barry Warsaw2003-12-301-1/+1
|
* remove ancient cruftFred Drake2003-12-301-4/+0
|
* - make "--" in code text not get converted to "-"Fred Drake2003-12-301-7/+21
| | | | - fix minor typo in comment
* - remove crufty markup that's no longer needed to make theFred Drake2003-12-301-3/+3
| | | | | presentation work right (and didn't work anyway) - fix minor typo
* use consistent email address for TimFred Drake2003-12-303-3/+3
|
* - update Tim's email addressFred Drake2003-12-301-4/+2
| | | | - remove spurious blank lines
* Add IPV6_ socket options from RFCs 3493 and 3542. Fixes #867012.Martin v. Löwis2003-12-301-0/+71
|
* Fix gcc 3.3 warnings related to Py_UNICODE_WIDE.Hye-Shik Chang2003-12-292-3/+24
|
* complete backout of listobject.c v2.171Andrew MacIntyre2003-12-283-13/+0
|
* Revert previous two checkins to repair test failure.Jeremy Hylton2003-12-261-24/+6
| | | | | | The special-case code that was removed could return a value indicating success but leave an exception set. test_fileinput failed in a debug build as a result.
* Fix name problem in previous checkin: Dict not ListJeremy Hylton2003-12-261-1/+1
|
* At 2.2, the Py<type>_Check() family of API functions (macros) changedAndrew MacIntyre2003-12-261-0/+1
| | | | | | | | | | | | semantics to include subtypes. Most concrete object APIs then had a Py<type>_CheckExact() macro added to test for an object's type not including subtypes. The PyDict_CheckExact() macro wasn't created at that time, so I've added it for API completeness/symmetry - even though nobody has complained about its absence in the time since 2.2 was released. Not a backport candidate.
* reverting 2.29: the patch was Ok, but the commit msg wrongAndrew MacIntyre2003-12-261-1/+0
|
* use the correct macro to access list sizeAndrew MacIntyre2003-12-261-1/+1
|
* At 2.2, the Py<type>_Check() family of API functions (macros) changedAndrew MacIntyre2003-12-261-0/+6
| | | | | | | | | | | | semantics to include subtypes. Most concrete object APIs then had a Py<type>_CheckExact() macro added to test for an object's type not including subtypes. The PyDict_CheckExact() macro wasn't created at that time, so I've added it for API completeness/symmetry - even though nobody has complained about its absence in the time since 2.2 was released. Not a backport candidate.
* The semantics of PyList_Check() and PyDict_Check() changed at 2.2, alongAndrew MacIntyre2003-12-261-0/+1
| | | | | | | | | with most other concrete object checks, but the docs weren't brought into line. PyList_CheckExact() was added at 2.2 but never documented. backport candidate.
* The semantics of PyList_Check() and PyDict_Check() changed at 2.2, alongAndrew MacIntyre2003-12-251-2/+12
| | | | | | | | | with most other concrete object checks, but the docs weren't brought into line. PyList_CheckExact() was added at 2.2 but never documented. backport candidate.
* Performance of list([]) in 2.3 came up in a thread on comp.lang.python,Andrew MacIntyre2003-12-253-6/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | which can be reviewed via http://coding.derkeiler.com/Archive/Python/comp.lang.python/2003-12/1011.html Duncan Booth investigated, and discovered that an "optimisation" was in fact a pessimisation for small numbers of elements in a source list, compared to not having the optimisation, although with large numbers of elements in the source list the optimisation was quite beneficial. He posted his change to comp.lang.python (but not to SF). Further research has confirmed his assessment that the optimisation only becomes a net win when the source list has more than 100 elements. I also found that the optimisation could apply to tuples as well, but the gains only arrive with source tuples larger than about 320 elements and are nowhere near as significant as the gains with lists, (~95% gain @ 10000 elements for lists, ~20% gain @ 10000 elements for tuples) so I haven't proceeded with this. The code as it was applied the optimisation to list subclasses as well, and this also appears to be a net loss for all reasonable sized sources (~80-100% for up to 100 elements, ~20% for more than 500 elements; I tested up to 10000 elements). Duncan also suggested special casing empty lists, which I've extended to all empty sequences. On the basis that list_fill() is only ever called with a list for the result argument, testing for the source being the destination has now happens before testing source types.
* add definitions required for expat 1.95.7Andrew MacIntyre2003-12-251-1/+1
|
* [Bug #850823] Fix broken linkAndrew M. Kuchling2003-12-231-1/+1
|
* [Bug #850818] Accept Gregory H. Ball's suggested rewrite of a confusing ↵Andrew M. Kuchling2003-12-231-3/+4
| | | | description
* [Bug #857821] Remove mention of deprecated string.{atol,atof} functions. ↵Andrew M. Kuchling2003-12-231-4/+2
| | | | (Patch from Gerrit Holl)
* Fix silly typoAndrew M. Kuchling2003-12-231-1/+1
|
* As part of fixing bug #829532, add a test case that exercises os.makedirsAndrew M. Kuchling2003-12-231-1/+36
|
* [Bug #829532] Invoking os.makedirs() with an argument that contains aAndrew M. Kuchling2003-12-231-0/+2
| | | | | | | directory name with a single dot fails. The patch skips creating directories named os.curdir. (Patch by Bram Moolenaar) 2.3 bugfix candidate.
* Fix unicode.rsplit()'s bug that ignores separater on the end of string whenHye-Shik Chang2003-12-232-1/+3
| | | | using specialized splitter for 1 char sep.
* Changed the UCHAR_MAX error msg a bit: we don't really assume anythingTim Peters2003-12-221-1/+1
| | | | | about "characters", we assume something about C's char type (which is an integral type).
* There are places in Python which assume bytes have 8-bits. Formalize that aSkip Montanaro2003-12-222-4/+8
| | | | | | bit by checking the value of UCHAR_MAX in Include/Python.h. There was a check in Objects/stringobject.c. Remove that. (Note that we don't define UCHAR_MAX if it's not defined as the old test did.)
* (forced commit)Hye-Shik Chang2003-12-220-0/+0
| | | | Previous revision was a fix for a problem by not 2.204 but 2.205.
* Fix broken xmlcharrefreplace by rev 2.204.Hye-Shik Chang2003-12-221-3/+3
| | | | (Pointy hat goes to perky)
* Make sure the UserDict copies do not share the same underlyingRaymond Hettinger2003-12-211-1/+1
| | | | | | | dictionary as the original. This parallels MvL's change to Lib/os.py 1.56. Backport candidate.
* Python 2.3.3 Window build number and release date.Thomas Heller2003-12-201-0/+2
|
* Add the first of (hopefully) many third-party licenses and acknowledgements.Raymond Hettinger2003-12-201-0/+59
|