This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | ajaksu2 |
|---|---|
| Recipients | ajaksu2, facundobatista, theller |
| Date | 2008年04月02日.20:13:14 |
| SpamBayes Score | 0.5648242 |
| Marked as misclassified | No |
| Message-id | <1207167195.85.0.921951767671.issue2534@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Thomas: I confirm your patch triggers this behavior. I can reliably get a __subclasscheck__ error by trying to "import sys" after the bogus catching happens: >>> def g(): ... try: ... return g() ... except ValueError: ... return sys.exc_info() ... >>> g() (<type 'exceptions.RuntimeError'>, 'maximum recursion depth exceeded while calling a Python object', <traceback object at 0xb7d9ba04>) >>> import sys Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: maximum recursion depth exceeded in __subclasscheck__ I hope this helps... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月02日 20:13:15 | ajaksu2 | set | spambayes_score: 0.564824 -> 0.5648242 recipients: + ajaksu2, theller, facundobatista |
| 2008年04月02日 20:13:15 | ajaksu2 | set | spambayes_score: 0.564824 -> 0.564824 messageid: <1207167195.85.0.921951767671.issue2534@psf.upfronthosting.co.za> |
| 2008年04月02日 20:13:14 | ajaksu2 | link | issue2534 messages |
| 2008年04月02日 20:13:14 | ajaksu2 | create | |