summaryrefslogtreecommitdiffstats
path: root/Lib/test
Commit message (Collapse)AuthorAgeFilesLines
* Maintain peepholer's cumlc invariant by updating the running totalRaymond Hettinger2004-11-021-3/+5
| | | | | | everytime a LOAD_CONSTANT is encountered, created, or overwritten. Added two tests to cover cases affected by the patch.
* * Bumped up the sleep() delay to four seconds so this test will runRaymond Hettinger2004-11-011-6/+9
| | | | | | reliably on WinME with FAT32. * Native speaker rewrite of the comment block. * Removed unnecessary backslashes from the multi-line function defintions.
* Add error checks for the bz2, cStringIO and operator modules.Walter Dörwald2004-11-013-0/+108
| | | | Add function names to various PyArg_ParseTuple calls in bz2module.c.
* Bug #1057993: Use sleep() always instead of os.utime() possibly brokenHye-Shik Chang2004-11-011-9/+5
| | | | in some platforms.
* SF patch #1056967, changes the semantics of Template.safe_substitute() to notBarry Warsaw2004-11-011-10/+9
| | | | raise a ValueError for dangling delimiters (the delimiter itself is returned).
* test_on_error(): Rewrite so it works on WinXP too. Unsure about 95/98/ME.Tim Peters2004-11-011-7/+13
|
* Bug #1048941: shutil.rmtree error handling was always brokenJohannes Gijsbers2004-10-311-3/+28
| | | | | Rewrite rmtree again, this time without os.walk(). Error handling had been broken since Python 2.3, and the os.walk() version inherited this.
* SF 1055820: weakref callback vs gc vs threadsTim Peters2004-10-301-0/+199
| | | | | | | | In cyclic gc, clear weakrefs to unreachable objects before allowing any Python code (weakref callbacks or __del__ methods) to run. This is a critical bugfix, affecting all versions of Python since weakrefs were introduced. I'll backport to 2.3.
* Wrote down the invariants of some common objects whose structure isArmin Rigo2004-10-281-2/+11
| | | | | | | | | | exposed in header files. Fixed a few comments in these headers. As we might have expected, writing down invariants systematically exposed a (minor) bug. In this case, function objects have a writeable func_code attribute, which could be set to code objects with the wrong number of free variables. Calling the resulting function segfaulted the interpreter. Added a corresponding test.
* Trigger a few error cases in Modules/_codecsmodule.c.Walter Dörwald2004-10-281-0/+14
|
* Fix bug of implementation of algorithm for calculating the date from year, weekBrett Cannon2004-10-281-3/+18
| | | | | | | | of the year, and day of the week. Was not taking into consideration properly the issue of when %U is used for the week of the year but the year starts on Monday. Closes bug #1045381 again.
* Add a comment explains why we should modify mtime here.Hye-Shik Chang2004-10-271-2/+4
|
* Removed newly redundant embedded import.Tim Peters2004-10-271-1/+0
|
* Whitespace normalization.Tim Peters2004-10-272-5/+5
|
* Paper over bug 1054615 by passing sane values to os.utime().Tim Peters2004-10-271-2/+5
| | | | | | | | | | The underlying bug still exists, but also existed in 2.3.4: import.c's load_source_module() returns NULL if PyOS_GetLastModificationTime() returns -1, but PyOS_GetLastModificationTime() doesn't set any exception when it returns -1, and neither does load_source_module() when it gets back -1. This leads to "SystemError: NULL result without error in PyObject_Call" on an import that fails in this way.
* Update optparse module and test suite to Optik 1.5a2.Greg Ward2004-10-271-192/+214
|
* - Added tests for the string load/dump function.Just van Rossum2004-10-261-14/+113
| | | | | | - Added a chunk of plist data as generated by Cocoa's NSDictionary and verify we output the same (including formatting) - Changed the "literal" plist code to match the raw test data
* SF #737473: Show up-to-date source code in tracebacks always.Hye-Shik Chang2004-10-261-0/+41
| | | | | And add an optional argument 'filename' to linecache.checkcache() to enable checking caches per-file.
* SF bug #1053819: Segfault in tuple_of_constantsRaymond Hettinger2004-10-261-0/+17
| | | | | | | Peepholer could be fooled into misidentifying a tuple_of_constants. Added code to count consecutive occurrences of LOAD_CONST. Use the count to weed out the misidentified cases. Added a unittest.
* SF bug #1054139: serious string hashing error in 2.4b1Raymond Hettinger2004-10-261-0/+9
| | | | | _PyString_Resize() readied strings for mutation but did not invalidate the cached hash value.
* Whitespace normalization.Tim Peters2004-10-251-1/+1
|
* SF bug #1048870: call arg of lambda not updatingRaymond Hettinger2004-10-241-0/+9
|
* Removed test_close_fds, because it's too unreliable. We simply cannotPeter Astrand2004-10-211-10/+0
| | | | | know that the newly-started Python process only has 3 filedescriptors open. Fixes bug 1048808.
* Add test case for bug #1017553Andrew M. Kuchling2004-10-201-0/+9
|
* Add support for %U and %W to contribute to calculating the date when the yearBrett Cannon2004-10-181-0/+22
| | | | | | and day of the week are specified. Closes bug #1045381.
* SF #1048865: Fix a trivial typo that breaks StreamReader.readlines()Hye-Shik Chang2004-10-171-1/+12
|
* Fix and test weak referencing of itertools.tee objects.Raymond Hettinger2004-10-171-0/+8
|
* Invalid patterns to substitute and safe_substitute would crash since patternNeal Norwitz2004-10-171-0/+12
| | | | is not a local variable. Add a test case.
* remove_stderr_debug_decorations(): Always try the substitution. ElseTim Peters2004-10-141-3/+1
| | | | | this test failed under the combination of passing -O to a debug-build Python. Now all 4 of those pass ({debug, release} x {-O, no -O}).
* Get test to pass on amd64 (opteron). This is pretty hacky, butNeal Norwitz2004-10-141-2/+7
| | | | rangeobject.c has an #ifdef that is reached only when LONG_MAX != INT_MAX
* Fixed a small bug. doctest didn't handle unicode docstrings containingJim Fulton2004-10-132-2/+23
| | | | non-ascii characters.
* Don't spend quite as much time looking for leaks on Windows, whereFredrik Lundh2004-10-131-2/+4
| | | | it's rather expensive to create new processes.
* normalize case when comparing directory names (problem reported byFredrik Lundh2004-10-131-1/+2
| | | | "Khalid A. B." on python-dev)
* Add a comment explaining -kb.Martin v. Löwis2004-10-131-0/+1
|
* New helper remove_stderr_debug_decorations(). This test passes in aTim Peters2004-10-131-7/+24
| | | | | debug build on Windows now. More applications of the helper may be needed on non-Windows platforms.
* Kill several problems at once: test_poll() failed sometimes for me.Tim Peters2004-10-132-8/+11
| | | | | | | | | | | Turns out the mysterious "expected output" file contained exactly N dots, because test_poll() has a loop that *usually* went around N times, printing one dot on each loop trip. But there's no guarantee of that, because the exact value of N depended on the vagaries of scheduling time.sleep()s across two different processes. So stopped printing dots, and got rid of the expected output file. Add a loop counter instead, and verify that the loop goes around at least a couple of times. Also cut the minimum time needed for this test from 4 seconds to 1.
* test_stdout_none(): Don't print "banana" to the screen in the middleTim Peters2004-10-131-2/+5
| | | | | of the test. It's testing stdout in a different process, so it has to print something, but I didn't find "banana" to be self-explanatory.
* Windows test_creationflags() test: print msg to stderr informing theTim Peters2004-10-131-1/+2
| | | | | | tester that a DOS box is expected to flash. Slash the sleep from 2 seconds to a quarter second (why would we want to wait 2 seconds just to stare at a DOS box?).
* XXX about extreme expense of test_no_leaking() on Windows. I'm not sureTim Peters2004-10-131-0/+1
| | | | | | what this is trying to do. If it's necessary for it to create > 1000 processes, it should be controlled by a new resource and not run by default on Windows.
* Experience with Zope2's tests showed it's a Bad Idea to make unittestTim Peters2004-10-121-45/+35
| | | | | | display a test's docstring as "the name" of the test. So changed most test docstrings to comments, and removed the clearly useless ones. Now unittest reports the actual names of the test methods.
* Wrap long lines.Tim Peters2004-10-121-43/+67
|
* Whitespace normalization.Tim Peters2004-10-121-17/+16
|
* Added Peter Astrand's subprocess module.Fredrik Lundh2004-10-122-0/+516
|
* Open source files in universal newlines mode.Michael W. Hudson2004-10-111-1/+1
|
* Locale data that contains regex metacharacters are now properly escaped.Brett Cannon2004-10-061-0/+13
| | | | Closes bug #1039270.
* Whitespace normalization.Tim Peters2004-10-031-1/+1
|
* SF bug #997050: Document, test, & check for non-string values in ↵David Goodger2004-10-031-12/+44
| | | | ConfigParser. Moved the new string-only restriction added in rev. 1.65 to the SafeConfigParser class, leaving existing ConfigParser & RawConfigParser behavior alone, and documented the conditions under which non-string values work.
* SF bug #1017864: ConfigParser now correctly handles default keys, processing ↵David Goodger2004-10-031-0/+10
| | | | them with ``ConfigParser.optionxform`` when supplied, consistent with the handling of config file entries and runtime-set options.
* 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())
generated by cgit v0.12 at 2025-12-28 04:59:01 (GMT)