Grzegorz Śliwiński

on hold, awaits newer sqlalchemy https://github.com/sqlalchemy/sqlalchemy/issues/6842

Everything seems legit and same according to documentation I used something like this over a year ago within a project I coded: ``` python # overriding pyramid_fullauth config.override_asset( to_override='pyramid_fullauth:resources/templates/', override_with='package.admin_app:resources/templates/registerlogin/')...

@robertlagrant could you also point me to that bug report? I'm very interested in whatever you'll be able to find!

Hmmm... Ad 4. And route redirections... It should be possible to override the routes settings altogether by committing configuration (http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/api/config.html#pyramid.config.Configurator.commit) after including pyramid_fullauth, and before assigning same routes to different...

Okay, let's do first step, and transfer all configuration into imperative one (though I like the declarative better ;) First step - #54

@Zitrax wouldn't it be possible to just add these two lines to your app config? ``` python configurator.add_jinja2_renderer('.mako') config.include('pyramid_fullauth') ``` I mean if you don't rely on any other mako...

It would be great :)

Okay, it looks like it fails on the first request to load? What's your session configuration? I have to admit It's the place I'd expect this to happen the least.

Okay then... this should not have happened... groupfinder doesn't have much in it to justify such behaviour. and neither does request.user.... You're using transactions package, right?

@Zitrax basically all of the auth factories are set only if they haven't been set already. So possibly all of that could be described. Either that, or add the possibility...