Closed haard closed 10 years ago
I'll give it a :+1:. I'll wait a day or 2 and merge this if @pydanny has no objections.
Thanks for the patch.
Unfortunately, I suspect this is going to fail. I've done enough Python 2/3 compat work to know there is enough in the code base to make 2to3 not operate very well. So what I'm going to do is add Python 3 to the travis.yml file and see what happens in the tests.
I expect there'll pop up more errors, but I'll fix and contribute them as I find them. The build scripts (e.g. installing unittest2) is a problem for CI builds right now.
Yeah, Travis fails out. :P
Is it possible to run build steps conditionally on version, or ignore the error? The actual tests does run on 3.3
I did something like that in dj-stripe. Having trouble paying with me phone. :(
Looks like you got it figured out. I added the Python 3 classified and bumped the version on PyPI. This way it will show up on Django Packages as being Python 3 compliant. People will try it and report errors. Ah yes...beta indeed. :wink:
Added 2to3 to setup.py and did the simplest patch possible for the updated ImportError message in Python 3. Tests pass on Python 3.3, happy-testing the UI seems to work.