summaryrefslogtreecommitdiffstats
path: root/Lib/test
Commit message (Collapse)AuthorAgeFilesLines
* SF patch #455966: Allow leading 0 in float/imag literals.Tim Peters2001-08-301-0/+44
| | | | Consequences for Jython still unknown (but raised on Jython-Dev).
* Add testcases for inheritance from tricky builtins (numbers, strings,Guido van Rossum2001-08-301-0/+74
| | | | tuples).
* Revert the previous patch to test_pow.py and move the test to test_unary.pyFred Drake2001-08-302-10/+8
| | | | | based on a suggestion from Tim Peters; also make sure that we're really doing exponentiation and not multiplication.
* Added a regression test for the negation-of-exponentiation optimizationFred Drake2001-08-301-0/+11
| | | | bug from compile.c. (SF bug #456756.)
* Add a new function imp.lock_held(), and use it to skip test_threaded_importTim Peters2001-08-301-4/+6
| | | | when that test is doomed to deadlock.
* Workaround by Tim Peters to skip this test if run from test.autotest,Jack Jansen2001-08-291-1/+5
| | | | | in which case it will hang because the import lock is already held by the main thread.
* Add tests for augmented floor divisionJeremy Hylton2001-08-292-0/+27
|
* Now that int is subclassable, have to change a test that tests forGuido van Rossum2001-08-291-2/+2
| | | | non-subclassability. (More tests for number subclassing should follow.)
* marshal.c r_long64: When reading a TYPE_INT64 value on a box with 32-bitTim Peters2001-08-291-0/+41
| | | | ints, convert to PyLong (rather than throwing away the high-order 32 bits).
* pickle.py, load_int(): Match cPickle's just-repaired ability to unpickleTim Peters2001-08-281-0/+15
| | | | | | | | 64-bit INTs on 32-bit boxes (where they become longs). Also exploit that int(str) and long(str) will ignore a trailing newline (saves creating a new string at the Python level). pickletester.py: Simulate reading a pickle produced by a 64-bit box.
* Update an email address.Barry Warsaw2001-08-281-10/+10
|
* Fix the test again due to fewer calls to __getattr__.Guido van Rossum2001-08-281-3/+1
|
* Fix one test to reflect the change in method lookup policy.Guido van Rossum2001-08-281-2/+1
|
* Added list of tests expected to be skipped on the mac.Jack Jansen2001-08-281-0/+36
|
* A quick hack to make the test pass on the Mac (similar to the quick hackJack Jansen2001-08-271-0/+4
| | | | to make it pass on Windows:-).
* Fix another test still expecting overflow on big int literals.Tim Peters2001-08-271-7/+2
|
* Change test_overflow to test_no_overflow; looks like big int literalsTim Peters2001-08-271-4/+5
| | | | | are auto-coerced to longs now, but this test still expected OverflowError. I can't imagine this test failure was unique to Windows.
* SF bug [#455775] float parsing discrepancy.Tim Peters2001-08-271-0/+15
| | | | PyTokenizer_Get: error if exponent contains no digits (3e, 2.0e+, ...).
* Undo previous checkin -- Barry fixed it better.Guido van Rossum2001-08-241-2/+0
|
* Update test output to match new (more informative) error message aboutGuido van Rossum2001-08-241-2/+2
| | | | calling unbound method with wrong first argument.
* Quick and dirty fix for test_extcall failures trigged by Guido'sBarry Warsaw2001-08-242-4/+8
| | | | | | | recent classobject.c change. When calling an unbound method with no instances as first argument, the error message has changed. The message now contains the class name, but the output text being compared to is too generic, so skip printing it.
* Remove the local 'getset' class -- this is now a built-in type withGuido van Rossum2001-08-241-18/+0
| | | | the same signature.
* Rip the import repr truncation test out of here and put it in test_repr.pyBarry Warsaw2001-08-241-35/+0
|
* Added lots of tests for reprs of "simple" objects, such as file,Barry Warsaw2001-08-241-0/+156
| | | | | | | lambda (anonymous functions?), function, xrange, buffer, cell (need to fill in), and (some) descriptor types. Also added a new test case for testing repr truncation fixes.
* supers(): typo -- "if verify" should be "if verbose".Guido van Rossum2001-08-241-1/+1
|
* Add test suite for super().Guido van Rossum2001-08-241-0/+32
|
* Add a test for the new getset type.Guido van Rossum2001-08-241-0/+24
|
* Looks like someone forgot the change the expected output file.Tim Peters2001-08-241-14/+14
|
* Add a test for the new // operator too.Tim Peters2001-08-231-0/+4
|
* SF bug [#454456] int overflow code needs tests.Tim Peters2001-08-231-0/+61
| | | | | Added tests for boundary cases in magical PEP 237 int->long auto-overflow, but nothing here addresses the rest of the bug report so left it open.
* Remove test_long's expected-output file.Tim Peters2001-08-232-9/+8
|
* Committing and closing SF patch #441348 to help Jython to pass this test.Finn Bock2001-08-231-1/+1
|
* Turn OverflowWarning into an error locally, in order to make theGuido van Rossum2001-08-231-0/+3
| | | | OverflowError test succeed.
* Merge changes from r22a2-branch back into trunk. Also, change patchBarry Warsaw2001-08-221-0/+3
| | | | level to 2.2a2+
* A test of SSL support, using a roundabout method suggested by Guido.Barry Warsaw2001-08-201-0/+13
| | | | However, this is only enabled with regrtest's --use=network switch.
* Use test_support.requires() to decide whether additional largefileBarry Warsaw2001-08-201-7/+8
| | | | tests should be run.
* Removed --have-resources flag in favor of the more granular -u/--useBarry Warsaw2001-08-201-22/+61
| | | | | | | | | | | | | | | | | | | flag, which specifies external or resource intensive tests to perform. This is used by test_largefile and test_socket_ssl. -u/--use takes a comma separated list of flags, currently supported: largefile, network. usage(): New function. Note that the semantics of main() have changed slightly; instead of returning an error code, it raises a SystemExit (via sys.exit()) with the given error code. main(): use_large_resources => use_resources Also, added support for long-option alternative to the short options. _expectations: Added test_socket_ssl to the list of expectedly skipped tests.
* use_large_resources => use_resourcesBarry Warsaw2001-08-201-2/+8
| | | | | | | | requires(): New function which can be used to `assert' that a specific -u/--use resource flag is present. Raises a TestSkipped if not. This is used in test_largefile and test_socket_ssl to enable external or resource consumptive tests that are normally disabled.
* Test failed because these was no expected-output file, but always printedTim Peters2001-08-201-5/+8
| | | | | | | to stdout. Repaired by not printing at all except in verbose mode. Made the test about 6x faster -- envelope analysis showed it took time proportional to the square of the # of tasks. Now it's linear.
* Deal more appropriately with bare ampersands and pointy brackets; thisFred Drake2001-08-201-7/+27
| | | | | | | | module has to deal with "class" HTML-as-deployed as well as XHTML, so we cannot be as strict as XHTML allows. This closes SF bug #453059, but uses a different fix than suggested in the bug comments.
* Add test case to cover multiple future statements on separate lines ofJeremy Hylton2001-08-201-0/+11
| | | | a module.
* Fix SF bug [ #450245 ] Error in parsing future stmtsJeremy Hylton2001-08-203-0/+5
| | | | | Add test case to cover multiple future statements on separate lines of a module.
* Committing and closing SF patch #403671 by Finn Bock to help JythonBarry Warsaw2001-08-201-11/+31
| | | | pass these tests.
* add a few test cases for threading module.Skip Montanaro2001-08-201-0/+52
|
* Silence warnings during test_osJeremy Hylton2001-08-201-0/+5
|
* Expose the CO_xxx flags via the "new" module (re-solving a problem "theTim Peters2001-08-181-0/+13
| | | | | | | | | | right way"). Fiddle __future__.py to use them. Jeremy's pyassem.py may also want to use them (by-hand duplication of magic numbers is brittle), but leaving that to his judgment. Beef up __future__'s test to verify the exported feature names appear correct.
* Fix for bug [#452230] future division isn't propagated.Tim Peters2001-08-171-0/+1
| | | | | | | builtin_eval wasn't merging in the compiler flags from the current frame; I suppose we never noticed this before because future division is the first future-feature that can affect expressions (nested_scopes and generators had only statement-level effects).
* Use raw-unicode-escape for the tests that require it.Martin v. Löwis2001-08-172-3/+3
|
* Add test for weak references.Guido van Rossum2001-08-171-3/+33
|
* Test that uu.py will not override an existing file if out_file isn'tBarry Warsaw2001-08-171-0/+34
| | | | given and the path is gleaned from the uu header.