'spacy' is a package and cannot be directly executed #2514
Comments
|
Thanks for the report. I'm pretty sure this is related to #2462 – for some reason in some situations, users who install via conda end up with an old version of spaCy. Like, a really really old one, the one that the official Anaconda distribution used to ship and that didn't have CLI commands yet. If you still have your install logs, could you check if there's some hint at that? Maybe conda didn't actually install the latest version from conda-forge, because your local Anaconda distribution already had spaCy included (but an old version)? And does |
|
@DSamuylov, not sure if you solved this, but the solution @BBCMax alluded to in his second comment of the thread @ines refers to worked for me. I'm also on Ubuntu 18.04 and py3.6 via anaconda. Although now I'm having this problem, though that seems solvable. :-) |
|
@drussellmrichie Do you still have your install logs and could you check if there's anything in them that looks like an old version of spaCy was used? Like, which command did you run and what exactly was conda doing there that resulted in you ending up with an old version? I'd love to get to the bottom of this and see if there's anything we can do to prevent this. This is such a weird problem and unfortunately, it's mostly been hitting new users which is extra frustrating. Btw, about the download timeout problem: If you want full control over how it's downloaded, I'd suggest finding the direct link to the archive file via the model releases. The model details also list the file size, so you can decide how you want to download it and what works best for you. |
|
@ines, happy to help if I can. Not sure if I have install logs (how would I find those?), but I just did I think that last line must have been how I got the old version of spacy on my machine (which I only got a few weeks ago). |
|
@drussellmrichie Thanks so much! (And not sure if conda saves the logs – I was mostly thinking about that detailed table it prints that tells you what it's going to install and update, but that might only be available in the scrollback.) So in this case, we can rule out an old Anaconda distribution then. My other theory was that maybe you have some other package installed (maybe a dependency of something else) that conflicts with one of spaCy's dependencies. So instead of updating all of the other dependencies, conda then just serves you an old version of spaCy that's compatible with the constraints. Do you remember which packages you installed explicitly since getting the new machine? |
|
Through some more greping through my terminal history, it seems that, after installing spacy, I installed tqdm and gensim through conda, and textblob-de and msgpack through pip. |
|
@drussellmrichie Thanks! (And sorry for asking you all these random questions, but I really want to get to the bottom of this issue and I feel like we're very close here.) Do you remember if you installed anything before you installed spaCy? |
|
No worries about the questions. This is the absolute least I can do after using spaCy for free. :-) Here's what I installed through the command-line ( I also installed pycharm, atom, dropbox, and skype, I think through some installers (not through commandline), but not sure if I did those before or after installing spacy. |
|
@drussellmrichie Thanks! There's nothing here that looks problematic. Basically, I'm trying to figure out if there could have been something in your Anaconda environment before you installed spaCy that caused conda to download and install an old version of spaCy (e.g. to ensure compatibility). A similar problem also just came up in #2542. The user didn't have access to the install log anymore, but shared the update log. Copying it over here for further investigation: |
|
Unfortunately, I don't think I have a way to look at the output from when I ran the update days ago. =( But my output must have looked similar to that. Let me know if there's anything else I can do. |
|
Quick update on my experiments: I used a clean VM, installed the latest version of the Anaconda distribution and tried to install spaCy using various commands. It always gave me Setup
Commands testedconda install spacy
conda install spacy -c conda-forge
conda install spacy -c anacondaResultResult of
|
|
Update: After reading through condas debugging logs, I think we found the culprit – The bad news: As a result, installing spaCy from the recent Anaconda distribution will currently download The good news: We can fix this by publishing a patch release to Thinc that requires |
|
Thanks, ines, for analyzing this problem! I saw that you worked on the patch, We are about to introduce students to text mining and want to bring them in contact with the power of SpaCy. :-) Edit: After a "conda update --all" spacy: 2.0.11-py36hf8a1672_1 is offered. Perfect! Thanks a million! |
|
"The good news: We can fix this by publishing a patch release to Thinc that requires msgpack." @ines : Is this issue fixed now? I still have the same issue |
|
I installed using conda install spacy, got the old version. conda update --all didn't help, so i did conda uninstall spacy, and then pip install spacy. solved the issue. |
|
We published new versions of spaCy and an updated recipe for Thinc on conda install spacy -c conda-forgeI just tested it on a VM using Ubuntu and a clean install of the latest Anaconda distribution. Sorry this took so long – this was really frustrating to debug 😭 Once the official Anaconda channel updates their builds of spaCy and Thinc, the problem should also be resolved when you only run |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
How to reproduce the behaviour
As described in the documentation, I run the following command to install spaCy:
However, if I call:
It fails with the following error message:
Your Environment
The text was updated successfully, but these errors were encountered: