Zsolt Ero

Yes, I agree, unpacking a JSON on every keypress is absolutely crazy, no matter what Jedi is used. And caching that is such a simple fix actually!

@DamnWidget if I remove the pipfile support from #720, would you be willing to merge the JSON caching fix?

In theory it saves him an `if os.path.exists(environfile) and os.path.isfile(environfile):` but I doubt it'd give high CPU usage. @jamesandres can you try 2.1.18?

I still don't understand what is the problem of caching it. People almost never change their interpreter path, definitely not between every keypress.

I believe my caching only needs a tab to be reopened, not an ST3 restart. On 24 November 2017 at 12:06, Oscar Campos wrote: > The problem with caching it...

@DamnWidget OK, I'll make a clean PR and test it properly before submitting it.

Here are my packages: ``` "installed_packages": [ "Anaconda", "Clickable URLs", "Compare Side-By-Side", "Dockerfile Syntax Highlighting", "Filter Lines", "HexViewer", "INI", "JavaScriptNext - ES6 Syntax", "Jinja2", "LESS", "Neon Color Scheme", "Package Control",...

So far, I've changed my Anaconda dir to be git controlled and added it to package control. Now the issue is not present, even if I go back to 2.1.16,...

Do you mean that Anaconda isn't inserting `path` in `os.path.isfile(path)`? It definitely does it for me. If I disable it won't happen, if I enabled it does. I'll look into...

Yes, normally it just inserts the code and selects it. But in that buggy / laggy version interaction it was inserting it about a second or two after I started...