| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
1. Acknowledge the welknown difference that jython
allows continue in the finally clause.
2. Avoid using _testcapi when running with jython.
This closes patch "[ #490417 ] Jython and test_exceptions"
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add raise_exception() to the _testcapi module. It isn't a test, but
the C API exists only to support test_exceptions. raise_exception()
takes two arguments -- an exception class and an integer specifying
how many arguments it should be called with.
test_exceptions uses BadException() to test the interpreter's behavior
when there is a problem instantiating the exception. test_capi1()
calls it with too many arguments. test_capi2() causes an exception to
be raised in the Python code of the constructor.
|
|
|
|
| |
OverflowError test succeed.
|
|
|
|
| |
just like reload(sys). Test that this is so. Closes SF bug #422004.
|
|
|
|
| |
SF patch 102989 by Thomas Wouters
|
| |
|
|
|
|
| |
various illegal uses of "continue".
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python test suite. Specifically,
- import time instead of strop in test_b1
- test for ClassType of exceptions using isinstance instead of
equality in test_exceptions
- remove __builtins__ from dir() output in test_pkg
test_pkg output needs to be regenerated.
|
|
|
|
|
|
|
| |
used for indentation related errors. This patch includes Ping's
improvements for indentation-related error messages.
Closes SourceForge patches #100734 and #100856.
|
|
|
|
| |
raised, caught, and converted to a string.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|