Wondering how we are going to solve python3 issue?

(In reply to Tomas Pelka from comment #2)
> Wondering how we are going to solve python3 issue?

Was seemingly enough to drop the ([3.3]) from the AM_PYTHON in configure.ac …

I kind of jumped the gun. it built, but doesn't run.

Some of the porting changes are pretty small (changing chr to unichr, renaming urllib.parse to urlparse, that kind of thing).  it also uses a faulthandler module that's available in python2 but we don't ship it.  That could be stripped out pretty easily.

It's a bunch of small changes, but adds up. I think we should backpedal and avoid rebasing after all.  I'll untag the build and revert it in version control.

okay untagged and reverted. devnak for 7.6

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.