summaryrefslogtreecommitdiffstats
path: root/Lib
Commit message (Collapse)AuthorAgeFilesLines
* Fix test for FeedParser results.Barry Warsaw2004-10-031-2/+2
|
* as_string(): Indicate that this mangles From_ lines.Barry Warsaw2004-10-031-1/+2
|
* Big email 3.0 API changes, with updated unit tests and documentation.Barry Warsaw2004-10-0324-371/+230
| | | | | | | | | | | | | | | | | Briefly (from the NEWS file): - Updates for the email package: + All deprecated APIs that in email 2.x issued warnings have been removed: _encoder argument to the MIMEText constructor, Message.add_payload(), Utils.dump_address_pair(), Utils.decode(), Utils.encode() + New deprecations: Generator.__call__(), Message.get_type(), Message.get_main_type(), Message.get_subtype(), the 'strict' argument to the Parser constructor. These will be removed in email 3.1. + Support for Python earlier than 2.3 has been removed (see PEP 291). + All defect classes have been renamed to end in 'Defect'. + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be added to messages that claim to be multipart but really aren't. + Updates to documentation.
* removed 2.2 supportJust van Rossum2004-10-021-74/+3
|
* use new readPlist() and writePlist() functionsJust van Rossum2004-10-021-7/+7
|
* Upon insertion, if memory runs out, the deque was left in a corrupted state.Armin Rigo2004-10-021-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | deque_item(): a performance bug: the linked list of blocks was followed from the left in most cases, because the test (i < (deque->len >> 1)) was after "i %= BLOCKLEN". deque_clear(): replaced a call to deque_len() with deque->len; not sure what this call was here for, nor if all compilers under the sun would inline it. deque_traverse(): I belive that it could be called by the GC when the deque has leftblock==rightblock==NULL, because it is tracked before the first block is allocated (though closely before). Still, a C extension module subclassing deque could provide its own tp_alloc that could trigger a GC collection after the PyObject_GC_Track()... deque_richcompare(): rewrote to cleanly check for end-of-iterations instead of relying on deque.__iter__().next() to succeed exactly len(deque) times -- an assumption which can break if deques are subclassed. Added a test. I wonder if the length should be explicitely bounded to INT_MAX, with OverflowErrors, as in listobject.c. On 64-bit machines, adding more than INT_MAX in the deque will result in trouble. (Note to anyone/me fixing this: carefully check for overflows if len is close to INT_MAX in the following functions: deque_rotate(), deque_item(), deque_ass_item())
* Which reminds me, I've had a much improved plistlib.py lying around forJust van Rossum2004-10-021-85/+113
| | | | | | ages. The main improvements are: - a much more convenient API: readPlist() and writePlist() - support non-dict top-level objects
* deque_traverse(): If the deque had one block, and its rightindex wasTim Peters2004-10-011-0/+9
| | | | | BLOCKLEN-1, this assert-failed in a debug build, or went wild with a NULL pointer in a release build. Reported on c.l.py by Stefan Behnel.
* Add tests for syntax errors.Raymond Hettinger2004-09-301-0/+13
|
* Expand scope to include general mapping protocol tests.Raymond Hettinger2004-09-301-0/+13
| | | | | | Many of these tests are redundant, but this will ensure that the mapping protocols all stay in sync. Also, added a test for dictionary subclasses.
* Add missing test_dict.py from patch #736962.Walter Dörwald2004-09-301-0/+404
|
* Improve test coverage.Raymond Hettinger2004-09-305-34/+49
|
* Improve test coverage.Raymond Hettinger2004-09-292-0/+45
|
* Improve test coverage.Raymond Hettinger2004-09-292-5/+116
|
* Reverted the addition of a NORMALIZE_NUMBERS option, per Tim Peter'sEdward Loper2004-09-282-180/+1
| | | | | | | | request. Tim says that "correct 'fuzzy' comparison of floats cannot be automated." (The motivation behind adding the new option was verifying interactive examples in Python's latex documentation; several such examples use numbers that don't print consistently on different platforms.)
* * Increase test coverage.Raymond Hettinger2004-09-281-0/+29
| | | | * Have groupby() be careful about decreffing structure members.
* Added a new NORMALIZE_NUMBERS option, which causes number literals inEdward Loper2004-09-282-1/+180
| | | | | the expected output to match corresponding number literals in the actual output if their values are equal (to ten digits of precision).
* Use Py_CLEAR(). Add unrelated test.Raymond Hettinger2004-09-281-0/+3
|
* Plug a leak and beef-up test coverage.Raymond Hettinger2004-09-281-0/+149
|
* Rename test for comparision errors.Raymond Hettinger2004-09-271-1/+1
|
* Beef-up tests for greater coverage and refcount checking.Raymond Hettinger2004-09-271-1/+59
|
* Patch #1011240: SystemError generated by struct.pack('P', 'foo').Armin Rigo2004-09-271-0/+1
|
* Trivial bug fix: deque == [] is not a good way to check if a deque is empty.Armin Rigo2004-09-271-1/+1
|
* Use floor division operator.Raymond Hettinger2004-09-277-8/+8
|
* Use floor division operator.Raymond Hettinger2004-09-271-3/+3
|
* - Added a "parser" option to testfile() and DocFileTest().Edward Loper2004-09-271-5/+12
|
* Checkin Tim's fix to an error discussed on python-dev.Raymond Hettinger2004-09-261-0/+5
| | | | | | | | | | | | | | | | | Also, add a testcase. Formerly, the list_extend() code used several local variables to remember its state across iterations. Since an iteration could call arbitrary Python code, it was possible for the list state to be changed. The new code uses dynamic structure references instead of C locals. So, they are always up-to-date. After list_resize() is called, its size has been updated but the new cells are filled with NULLs. These needed to be filled before arbitrary iteration code was called; otherwise, that code could attempt to modify a list that was in a semi-invalid state. The solution was to change the ob->size field back to a value reflecting the actual number of valid cells.
* Make the regex pattern easier to read, understand, and modifyRaymond Hettinger2004-09-261-4/+6
| | | | by factoring out the common prefix (the delimiter).
* Removed debug_script from the public API: no docs, not public. I'm inTim Peters2004-09-261-1/+0
| | | | | the process of writing docs for the other "missing" debug support functions.
* Add set_unittest_reportflags() to the public API. Docs will followTim Peters2004-09-261-0/+1
| | | | "soon", after I repair the LaTeX I somehow damaged.
* Removed two undocumented unittest support classes, and one undocumentedTim Peters2004-09-261-3/+0
| | | | | unittest support function, from the public interface. If they're not documented, they shouldn't be public.
* Removed most of the module docstring. There's too much to explain now,Tim Peters2004-09-251-124/+2
| | | | and the LaTeX docs are in increasingly good shape.
* Whitespace normalization.Tim Peters2004-09-241-1/+1
|
* Port test_unpack to doctest (patch #736962).Johannes Gijsbers2004-09-241-144/+131
|
* Add yet more tests for buffer().Neil Schemenauer2004-09-241-0/+11
|
* Add a few more tests for the buffer() object.Neil Schemenauer2004-09-241-0/+8
|
* Added log() functionVinay Sajip2004-09-241-0/+8
|
* Added exception handling during handler initialization in fileConfig()Vinay Sajip2004-09-241-24/+27
|
* Whitespace normalization.Tim Peters2004-09-241-1/+1
|
* Granted Noam Raphael's request for minor improvements to the re module andRaymond Hettinger2004-09-241-4/+4
| | | | | | | | | | | | | | its documentation. * Documented that the compiled re methods are supposed to be more full featured than their simpilified function counterparts. * Documented the existing start and stop position arguments for the findall() and finditer() methods of compiled regular expression objects. * Added an optional flags argument to the re.findall() and re.finditer() functions. This aligns their API with that for re.search() and re.match().
* SF bug #513866: Float/long comparison anomaly.Tim Peters2004-09-231-2/+102
| | | | | | | | | | | | | | | | | | When an integer is compared to a float now, the int isn't coerced to float. This avoids spurious overflow exceptions and insane results. This should compute correct results, without raising spurious exceptions, in all cases now -- although I expect that what happens when an int/long is compared to a NaN is still a platform accident. Note that we had potential problems here even with "short" ints, on boxes where sizeof(long)==8. There's #ifdef'ed code here to handle that, but I can't test it as intended. I tested it by changing the #ifdef to trigger on my 32-bit box instead. I suppose this is a bugfix candidate, but I won't backport it. It's long-winded (for speed) and messy (because the problem is messy). Note that this also depends on a previous 2.4 patch that introduced _Py_SwappedOp[] as an extern.
* Improve three recipes in the itertools docs.Raymond Hettinger2004-09-231-3/+9
|
* Arghh, checked in wrong draft. Replacing with correct one.Raymond Hettinger2004-09-231-3/+4
|
* Use local variables in StringIO.write().Raymond Hettinger2004-09-231-10/+11
| | | | Makes it easier on the eyes and a bit more snappy.
* Fix for SF bug #1029475 : reload() doesn't work with PEP 302 loaders.Phillip J. Eby2004-09-231-2/+16
|
* SF patch #1031667: Fold tuples of constants into a single constantRaymond Hettinger2004-09-221-3/+13
| | | | | | | | Example: >>> import dis >>> dis.dis(compile('1,2,3', '', 'eval')) 0 0 LOAD_CONST 3 ((1, 2, 3)) 3 RETURN_VALUE
* Bug #1030125: rfc822 __iter__ problemRaymond Hettinger2004-09-222-0/+14
| | | | Add iteration support to the Message class.
* Added getLoggerClass()Vinay Sajip2004-09-221-12/+15
|
* - Minor docstring fixes.Edward Loper2004-09-211-15/+9
| | | | - Simplified code to find names for file-based tests.
* - Changed SampleClass docstrings to test docstring parsing a littleEdward Loper2004-09-211-7/+18
| | | | more thouroughly.