python3 broken backtrace + typo about pudb

[asmeurer]

That's actually not a typo. That's how you have to do it for Python 2.4 and 2.5 support. But it doesn't work in Python 3. I don't know if there's a way around it.

[asmeurer]

See http://docs.python.org/3/howto/pyporting.html#capturing-the-currently-raised-exception.

[inducer]

The real issue is that I thought the installation script for pudb contained an invocation of 2to3, which should've made this issue disappear, but it did not. Fixed in 4f913f6. Please reopen if there's still an issue.

[asmeurer]

That's because you decided to use a single code base. If you switch to 2to3, there is a lot of code that can be simplified. I think you can probably delete the py3compat file completely.

[asmeurer]

See #1.

[inducer]

Wow. Goes to show how little I remember of the cr*p I said years ago. :) Re-fixed by 4059aeb.