Ralf Ramsauer

Had the same issues here. Try either to build gdev against an older boost version (e.g. 1.47) _or_ just remove the std::ref around (this). This used to work for me,...

First I'd like to discuss those issues, I didn't have a look into the code yet. Additionally I still have to check if this behaviour depends on python-levenshtein (which I'm...

I'm currently writing some patches. Think I will have to touch the check_for_none and check_empty_string decorators... Let me return with a pull request in a couple of hours.

Hi, before requesting to pull, [here](https://github.com/lfd/fuzzywuzzy/tree/fuzzfix) are the fixes. How can I run performance benchmarks? Thanks

Huh, that went quickly... Thanks for reviewing.

Same here.

Why printing an error message if this is a bug that can be fixed? I think it should rather be fixed than closed, but I'm not a Go guy...

A chdir() to the correct directory would be a hacky fix, but would avoid printing an error message for a bug that can definitely be fixed. But I technically see...

Hi, I can confirm this issue. This also happens for mis-encoded metadata in commits, like commit [dcb71129841e5821c0cbbdd4017a6f202f180108](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dcb71129841e5821c0cbbdd4017a6f202f180108) in the Linux kernel (look at the author name): Reconstruction: ``` import pygit2...

My local workaround is to use the raw members of the classes, and then let them through: ``` def fix_encoding(string): try: string = string.decode('utf-8') except: string = string.decode('iso8859') return string...