Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add g:ncm2_jedi#settings #4

Closed
theFool32 opened this issue Aug 4, 2018 · 3 comments
Closed

Add g:ncm2_jedi#settings #4

theFool32 opened this issue Aug 4, 2018 · 3 comments
Labels
WIP working in progress

Comments

@theFool32
Copy link

Some packages like numpy, torch, tensorflow are so large and it takes a long time to complete them.
Anyway to cache it ahead?
Thanks.

@antonzub1
Copy link

@roxma, first of all - thank you very much for doing great job and delivering such a good product. It works really well, except speed of completion on large packages, as @theFool32 mentioned. I am wondering - is it possible to utilize Jedi cache somehow to make completions more fast?

@roxma
Copy link
Member

roxma commented Aug 6, 2018

Thanks for the info @zabulazza

I will get some free time and test it.

@roxma
Copy link
Member

roxma commented Jan 21, 2019

@zabulazza

filesystem-cache is enabled by default.

I'm not sure what I can do for this.

You could try this fork for now: #6

I'm going to add g:ncm2_jedi#settings for customized settings for https://jedi.readthedocs.io/en/latest/docs/settings.html and then close this issue.

@roxma roxma changed the title How to cache large package? Add g:ncm2_jedi#settings Jan 21, 2019
@roxma roxma added the WIP working in progress label Jan 21, 2019
@roxma roxma closed this as completed in 0003b01 Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WIP working in progress
Projects
None yet
Development

No branches or pull requests

3 participants