Daniel Bengtsson

I was also looking for a dry-run. But when not finding it I hoped the real run would print out some info, but I only saw a list of updated...

I have hit the same issue. Is the status the same ? Are there no workaround if I want to use jinja templates ?

This might be an ugly hack, but I tried something like this to force usage of jinja without changing the fullauth source. ``` python def include_fullauth(config): """Need some patching to...

True, I just tried to avoid messing with my own config since it's a bit hacky. But not very likely that I will use both template systems at once in...

The workaround above still failed in some cases, where object_session returned None. Another seemingly more reliable version of avoiding that exception is to change the implementation of `user(request)` in `request.py`...

I am importing Session from pyramid_basemodel. I noticed one machine was on pyramid 1.6.1 and the other 1.7. But updating that made no difference.

I did notice that the traceback contained `pyramid_debugtoolbar` and indeed turning that off removed the problem. Turns out with that enabled groupfinder() is called twice and fails with the exception...

I wanted a generic name for the 's:user' so I basically changed the ('password_change', 'email_change') to 'user'. In addition I did not want to care about inactive vs active users...

A related confusing issue is that the pip package you need is **asciichartpy** not **asciichart**. Both these packages seem to exist, but the second one seem to be just empty.

Really annoying. The way to remove the storage setting seem to be to open the developer tools and find and delete it there.