Yaroslav Klyuyev

JFYI: I have not added any tests for new features. I do not know why coverage increased (it' something obvious but I do not want to investigate)

There may be several more universal alternatives: 1. `signing.dumps(...)` as code: 1. increase length of "code" field 2. store `signing.dumps(arbitrary_data)` in code field 3. it's now possible to use "new_email"...

builtin support for several css frameworks. And I think that with crispy forms you can use one template for both signin and signup form. self.helper.layout may be useful for defining...

I have updated yesterday and experience same problem.

Solved problem on my site. Please merge my pull request

looks like apache mod_wsgi: ``` mod_wsgi.listener_port = '27788' ```

There is a ready recipie (link from 2.7 docs). Will you adapt it? http://code.activestate.com/recipes/576611/

Can this be connected to following problem? After some massive changes in repo gitinspector consumes all the CPU with a lot of `git blame ...` and does not finish repo...

Thanks for reply. Maybe there are some options for optimizing history? Something like this: http://stevelorek.com/how-to-shrink-a-git-repository.html But I do not know if removing unused files from history will affect gitinspector as...

@adam-waldenberg And one more question: does gitispector blame files excluded by '-x' option?