It would seem Paste now supports Python3 (​source here). If we move back we can solve some issues we are having with gunircorn such as the one in #978.

It would seem since version 2.0 of Paste it's had experemental python 3 support, the 2.0.1 and 2.0.2 build on that.

Currently, when there is a new database with nothing that has been done, we skip all the sqlalchemy-migrate migrations and just make the models based off models.py, we then run the alembic migrations. This actually causes problems when we start doing structural changes in alembic as they have already been done in models.py so when the alembic migrations run, they error.

One solution could be to skip all the alembic migrations, however, I think a better solution is to not make any models off models.py and instead make the initial alembic migration create all the models in the state they're in right now and use alembic migrations to change them in the future, removing all of the code to construct models from model.py.

I've toyed a bit with template hooks, and I must say I'm not so very fond of it.

The thing I dislike is that you have to modify templates. That is to say that some part of the plugin behavior is outside of the plugin.

I think it'd be a way better idea to add an overriding system for plugins, in that order Base templates -> themes -> plugins (plugins win all the time).

That said, it can be a good idea to add hooks in some places you'd expect to be modified often (in the forms before the submit, at the end of media data's template...)