summaryrefslogtreecommitdiffstats
path: root/Lib/test
Commit message (Collapse)AuthorAgeFilesLines
* test_multilingual(): Test for Header.__unicode__().Barry Warsaw2002-06-291-0/+22
|
* Track change of begin() to _begin().Jeremy Hylton2002-06-281-2/+2
|
* Lots of new and updated tests to check for proper ascii headerBarry Warsaw2002-06-282-42/+187
| | | | | | | folding. Note that some of the Japanese tests have changed, but I don't really know if they are correct or not. :( Someone with Japanese and RFC 2047 expertise, please take a look!
* Added character data buffering to pyexpat parser objects.Fred Drake2002-06-281-1/+94
| | | | | | | | | Setting the buffer_text attribute to true causes the parser to collect character data, waiting as long as possible to report it to the Python callback. This can save an enormous number of callbacks from C to Python, which can be a substantial performance improvement. buffer_text defaults to false.
* Integrate the tests for name interning from PyXML (test_pyexpat.pyFred Drake2002-06-271-0/+18
| | | | revision 1.12 in PyXML).
* Suppress the variable verbose output from test.xmltests; the inclusion ofFred Drake2002-06-262-15/+3
| | | | timing information in the output makes the determination of success bogus.
* Add convenience module to run all the XML tests.Fred Drake2002-06-252-0/+395
|
* Fix SF bug 572567: Memory leak in object comparison.Raymond Hettinger2002-06-241-0/+12
|
* Add a check that the bug Jeremy just fixed in _PyTuple_Resize() isGuido van Rossum2002-06-211-0/+5
| | | | | | fixed. (Jeremy, how did you discover that?)
* SF 569257 -- Name mangle double underscored variable names in __slots__.Raymond Hettinger2002-06-201-0/+18
|
* Disable the test for importing very long lists for MacPython: it triggersJack Jansen2002-06-201-1/+2
| | | | | an out-of-memory condition (and a hang on OSX). Filed a bug report (#571845) to make sure this is eventually fixed.
* Removed the generator future-stmt -- not needed for 2.3.Tim Peters2002-06-201-1/+0
|
* I get failures half of the time that I run this, so I'll disableGuido van Rossum2002-06-201-2/+2
| | | | | running this as part of the regular test suite again, until I have time to figure out why.
* Fix the bug described inMichael W. Hudson2002-06-192-1/+50
| | | | | | | | | http://mail.python.org/pipermail/python-dev/2002-June/025461.html with test cases. Also includes extended slice support for arrays, which I thought I'd already checked in but obviously not.
* Michael fixed the race conditions and removed the sleeps.Guido van Rossum2002-06-181-9/+55
| | | | | This is his SF patch 569697. I renamed main() to test_main() again so that this is run as part of the standard test suite.
* Patch from SF bug 570483 (Tim Northover).Guido van Rossum2002-06-181-0/+6
| | | | | | In a fresh interpreter, type.mro(tuple) would segfault, because PyType_Ready() isn't called for tuple yet. To fix, call PyType_Ready(type) if type->tp_dict is NULL.
* Alter text test arg to obey new rule, also include inverse test to make ↵Piers Lauder2002-06-171-6/+5
| | | | time-zone independant
* test_module_with_large_stack(): This failed when Python was run with -O,Tim Peters2002-06-151-2/+5
| | | | | trying to delete a .pyc file that didn't exist (it needed to delete .pyo then).
* test_module_with_large_stack(): This failed on Windows, for the wrongTim Peters2002-06-151-1/+1
| | | | reason <wink>: can't unlink an open file on Windows.
* Test for the bug in recurse_down_subclasses() that I just fixed.Guido van Rossum2002-06-141-0/+10
|
* Fix SF bug # 561858 Assertion with very long listsNeal Norwitz2002-06-141-0/+31
| | | | | Write 4 bytes for co_stacksize, etc. to prevent writing out bad .pyc files which can cause a crash when read back in.
* SF bug # 493951 string.{starts,ends}with vs slicesNeal Norwitz2002-06-141-0/+27
| | | | Handle negative indices similar to slices.
* Test exceptional condition in select()Neal Norwitz2002-06-131-0/+7
|
* Test exceptional conditions in list.sort()Neal Norwitz2002-06-131-0/+15
|
* Fix for SF bug 532646. This is a little simpler than what NealGuido van Rossum2002-06-131-0/+14
| | | | | suggested there, based upon a better analysis (__getattr__ is a red herring). Will backport to 2.2.
* Temporarily disable the timeout and socket tests.Guido van Rossum2002-06-132-14/+14
| | | | | | They still run as standalone scripts, but when used as part of the regression test suite, they are effectively no-ops. (This is done by renaming test_main to main.)
* Hopefully this addresses the remaining issues of SF bugs 459235 andGuido van Rossum2002-06-131-0/+46
| | | | | | 473985. Through a subtle rearrangement of some members in the etype struct (!), mapping methods are now preferred over sequence methods, which is necessary to support str.__getitem__("hello", slice(4)) etc.
* Comment out testHostnameRes() -- it depends on a correctly workingGuido van Rossum2002-06-131-10/+10
| | | | DNS, and we can't assume that.
* Fix non-blocking connect() for Windows. Refactored the codeGuido van Rossum2002-06-131-12/+2
| | | | | | | | | | | that retries the connect() call in timeout mode so it can be shared between connect() and connect_ex(), and needs only a single #ifdef. The test for this was doing funky stuff I don't approve of, so I removed it in favor of a simpler test. This allowed me to implement a simpler, "purer" form of the timeout retry code. Hopefully that's enough (if you want to be fancy, use non-blocking mode and decode the errors yourself, like before).
* Major overhaul of timeout sockets:Guido van Rossum2002-06-132-4/+7
| | | | | | | | | | | | | | | | | | | | - setblocking(0) and settimeout(0) are now equivalent, and ditto for setblocking(1) and settimeout(None). - Don't raise an exception from internal_select(); let the final call report the error (this means you will get an EAGAIN error instead of an ETIMEDOUT error -- I don't care). - Move the select to inside the Py_{BEGIN,END}_ALLOW_THREADS brackets, so other theads can run (this was a bug in the original code). - Redid the retry logic in connect() and connect_ex() to avoid masking errors. This probably doesn't work for Windows yet; I'll fix that next. It may also fail on other platforms, depending on what retrying a connect does; I need help with this. - Get rid of the retry logic in accept(). I don't think it was needed at all. But I may be wrong.
* Fix a typo.Guido van Rossum2002-06-131-1/+2
| | | | Add a sleep (yuck!) to _testRecvFrom() so the server can set up first.
* Whitespace nit.Guido van Rossum2002-06-131-1/+1
|
* Remove some overly complicated ways to concatenate and repeat stringsGuido van Rossum2002-06-121-6/+7
| | | | using "".join(). Fold a long line.
* Don't test for Java, test for sys.getrefcount.Guido van Rossum2002-06-121-2/+2
|
* Some provisional changes to get more tests to run on Windows (I hope).Guido van Rossum2002-06-121-6/+8
|
* Argh. Typo. :-(Guido van Rossum2002-06-121-1/+1
|
* Allow absent fromfd(), for Windows.Guido van Rossum2002-06-121-0/+2
|
* testSetSockOpt() should not require the reuse flag to be 1 -- anyGuido van Rossum2002-06-121-2/+2
| | | | | nonzero value is OK. Also fixed the error message for this and for testGetSockOpt().
* Lose the message on assertEqual calls -- they actually hideGuido van Rossum2002-06-121-18/+15
| | | | information on what went wrong.
* Docstring, layout and style tweaking. Increase fuzz to 1 second.Guido van Rossum2002-06-121-90/+87
|
* Add some more basic tests to validate the argument checking ofGuido van Rossum2002-06-121-1/+51
| | | | | settimeout(), test settimeout(None), and the interaction between settimeout() and setblocking().
* New test suite for the socket module by Michael Gilfix.Guido van Rossum2002-06-123-180/+486
| | | | Changed test_timeout.py to conform to the guidelines in Lib/test/README.
* Add a testcase to ensure that cycles going through the __class__ linkGuido van Rossum2002-06-121-0/+6
| | | | of a new-style instance are detected by the garbage collector.
* SF bug 567538: Generator can crash the interpreter (Finn Bock).Guido van Rossum2002-06-121-0/+20
| | | | | | | | | | This was a simple typo. Strange that the compiler didn't catch it! Instead of WHY_CONTINUE, two tests used CONTINUE_LOOP, which isn't a why_code at all, but an opcode; but even though 'why' is declared as an enum, comparing it to an int is apparently not even worth a warning -- not in gcc, and not in VC++. :-( Will fix in 2.2 too.
* Fix for problem reported by Neal Norwitz. Tighten up calculation ofMichael W. Hudson2002-06-111-0/+2
| | | | slicelength. Include his test case.
* This is my nearly two year old patchMichael W. Hudson2002-06-112-1/+73
| | | | | | | | | [ 400998 ] experimental support for extended slicing on lists somewhat spruced up and better tested than it was when I wrote it. Includes docs & tests. The whatsnew section needs expanding, and arrays should support extended slices -- later.
* Patch #488073: AtheOS port.Martin v. Löwis2002-06-116-5/+48
|
* SF patch 564549 (Erik Andersén).Guido van Rossum2002-06-101-0/+11
| | | | | | | The WeakKeyDictionary constructor didn't work when a dict arg was given. Fixed by moving a line. Also adding a unit test. Bugfix candidate.
* Added -t (--threshold) option to call gc.set_threshold(N).Guido van Rossum2002-06-071-25/+30
|
* SF patch 555085 (timeout socket implementation) by Michael Gilfix.Guido van Rossum2002-06-062-10/+193
| | | | | | | | | | | | | I've made considerable changes to Michael's code, specifically to use the select() system call directly and to store the timeout as a C double instead of a Python object; internally, -1.0 (or anything negative) represents the None from the API. I'm not 100% sure that all corner cases are covered correctly, so please keep an eye on this. Next I'm going to try it Windows before Tim complains. No way is this a bugfix candidate. :-)
generated by cgit v0.12 at 2025-02-05 04:49:03 (GMT)