I was very surprised to see how small the team was but it looks like they have some great talent. A little bit off topic but the FastAPI creator works at explosion. Using FastAPI has been the most enjoyable Python web development experiences for me.

I'm gonna go for: "spyder"

Final answer

Was it too hard to understand or the reality is too ridiculous to even think about it being true? A friend of me had the same problem so I think everybody has it, if you have autocompletion when using Spacy then say it so you would add intellectual value to the thread by constraining the scope of this existential bug for the python Nlp industry.

Python libraries don't implement autocompletion, language servers or completion engines do. I suggest you configure your editor correctly, because spacy works just fine with vscode vim, or whatever have you.

Here's a screenshot: https://imgur.com/a/9bcgPkz

There's a lot that can go wrong with getting Python autocomplete working, and it's possible you are seeing something different. But I would suggest it is environmental rather than something Spacy is doing.

Autocompletion isn't a standard feature of any major NLP library, and blaming it on Python (currently the most popular language for NLP) isn't a good argument.

I install a package (spacy) I don't get any autocompletion of the API from the main spacy object and any other subsequent spacy data structure. Indeed autocompletion is usually on the language side but here it's a combination of the weaknesses of python and of the lazyness of spacy developers by making everything dynamic they broke the autocompletion that is normally working in python. Therefore it's not production ready, what else is there to say? I tried both pycharm and vscode

Actually it's the opposite of "making everything dynamic". spaCy is mostly implemented in Cython, which is a language for writing C extensions for Python. So things are statically typed and memory managed, which sometimes doesn't work well with inspect. We set whatever compilation flags we can to make the annotations passed through though. It's definitely not a question of laziness though...You could say we worked extremely hard to break things in this particular way.

In v3 we've been able to finally ditch Python 2 support, which means we're able to embrace type annotations. Our machine learning library, https://thinc.ai, is extensively type-annotated and actually you can get type hints and type errors for composing layers incorrectly.

Personally I use vim and don't use autocompletion, I find it makes the typing laggy and I've just never really wanted it. We do have developers on the team who use autocompletion though and I think spaCy actually supports it better than you suggest, I'm not sure whether you had a specific problem, but maybe see whether it works if you install spacy-nightly.

Btw I do think you've come across as a weird jerk in this thread though? You might want to read over your messages and think about that. Like, I (and I think most others) genuinely didn't get what you meant in your first few messages; I thought you were saying spaCy didn't let you _build_ autocomplete.

Many autocomplete implementations seem to struggle with anything that isn’t “pure python”; pyspark is notorious for it too.

...but, the type annotations do work! That’s definitely the right way to fix it.

Can’t wait~