Mikhail Korobov

In Python 3 `keys()` and alike methods don't just return iterators; they return key views which e.g. support membership checks, `__repr__` and `__str__` method which show values, len() method. AFAIK...

Hi @EgorLakomkin, I think it makes sense not to return duplicate keys. PRs are welcome :)

@farscape2012 you can use [BytesDAWG](http://dawg.readthedocs.io/en/latest/#bytesdawg) and encode/decode data yourselves.

@farscape2012 yes, values should be bytes. The only thing RecordTrie does differently from BytesDAWG is that it converts data to/from bytes using a predefined record format (it uses https://docs.python.org/3/library/struct.html from...

@farscape2012 key/value pairs are sorted by their binary value. Internally there are no values - values are just appended to corresponding keys after a separator, and the resulting strings are...

Underlying dawgdic C++ library doesn't allow zero bytes in keys (because it uses null-terminated strings) - that's why the wrapper disallows arbitrary bytestring keys. It stores utf8-encoded unicode and utf8...

See also: https://code.google.com/p/dawgdic/issues/detail?id=4&can=1

Hi Florian, I can't unfortunately merge this pull request as-is, because of the following reasons: - tests fail on Travis under Python 2.x; - the feature looks a bit odd...

Hi Florian, > Regarding the use case and the second two points, the whole change is all about getting the max speed/efficiency. If you want to scan a long string...

Hi Florian, Congratulations! Say hello to the new Leitner from me :) > Regarding the issue of memory-views, I must say I do miss a Java-like > CharSequence type in...