So, we have Python 3 support, but I wouldn't say that it's a "first class citizen" at present. In our next release (0.9.0 or maybe even sooner) we should be able to thoroughly recommend to users that they use Python 3.

The main trouble with this at present is related to #978, that gunicorn doesn't quite work with our deployment setup smoothly. We need to figure out how to solve this, whether using gunicorn or some other solution.

A user in IRC reported that trying to build against latest git master results in:

IOError: [Errno 2] No such file or directory: 'mediagoblin/_version.py' when making ./bin/python setup.py develop

_version.py was removed in ​https://gitorious.org/mediagoblin/mediagoblin/commit/e6121708e5d1297f92fcecfa4025b222e805c743 to be generated via configure.ac, but this appears to break setup.py (unless someone runs make first?).

setup.py requires six==1.5.2, citing build problems with newer versions. Pyrax, which is being considered to replace the deprecated py2-only Cloudfiles storage backend, has a dependency which requires a more recent version of six (see #715).

In my test environment, removing the constraint and installing a more recent versions of six appears to work fine. Can we remove the six=1.5.2 requirement?