rox
> and when ultisnips is enabled it shows snippet@0 even when I type request.pos and then select post. NCM caches the result when you typed `.`, in this case, you...
This gif shows my point. 
> Is it possible to disable cache altogether? Not possible with current version. The cache control is hard-coded by ncm's jedi source.
I decided to disable the caching of jedi source. You could test this PR #128
This is how it looks like. I believe it should still be considered as an upstream bug. 
It seems the no-cache version slows things down. And unfortunately this will make fuzzy matching impossible, since jedi doesn't have builtin fuzzy matching: https://github.com/davidhalter/jedi/issues/827
Maybe I should revert the change.
I've pushed another update. Please test it in case the no-cache is not the cause.
I think it's better to wait for the merge of the PR. I don't have much time for debugging new features recently.
Thanks for the info. Will look into that in my spare time.