The py3_work branch brings supports for py3. I try to keep it more or less up to date but there are quite a few if/then I'm not thrilled about.

Feel free to try to run it, so far I've been using the test suite to see if it runs on py3 or not but I am probably missing some cases.

So if you want to use pagure with py3, cool but be ready for a bumpy ride :)

Well, runserver works. I will do a pullrequest.

This needs a little more work than just running the test or using runserver, so it's not quite ready for a PR yet.

Sure, it is just a PR on py_work branch to share fixes on import for python3.

Ah ok cool then :)

Sorry I misunderstood your previous comment :)

Hi, what's current status for python3 support?

I can help with this transition but I have one question:
should pagure supports both py2 and py3, or just move to py3.

For example, there're a lot of codes dealing with unicode/bytes, of course we can use six to handle, but it's still painful. And some async program like ev-server uses trollius which is deprecated in favor of asyncio[1], however only py3 supports asyncio.

[1] http://trollius.readthedocs.io/deprecated.html

We'd probably want to use something like trololio to do Python 2 / Python 3 compatibility: http://trololio.readthedocs.io/

This is done with Pagure 5.0, so this can be closed.

Indeed :)