New click library version (8.1.0) breaks spaCy

[WBrandes]

How to reproduce the behaviour

Trying to import spaCy in a python terminal, or trying to download a model through the command line (python -m spacy download en_core_web_trf), gives:

ImportError: cannot import name 'get_terminal_size' from 'click.termui

Only ran into this because I just made a new AWS instance, and it installed the newest version of click, which was updated about an hour ago (just my luck). When I re-installed click as version 8.0.4 spaCy runs fine, but I expect anyone doing a clean install of Python will run into this issue.

Your Environment

• Operating System: Amazon Linux
• Python Version Used: 3.9.6
• spaCy Version Used: 3.2.3

[NikitaKamzeev]

I have the same issue with spaCy==3.2.0, python==3.7.10 and Amazon linux Operating System.

[philgooch]

According to the click 8.1.0 Release Notes: get_terminal_size is removed, use shutil.get_terminal_size instead.

[Mayank-Bhatia]

So what's the solution in the meantime, use older version of click after installing spacy?

[Mayank-Bhatia]

RUN pip uninstall click -y && pip install "click<8" in my Dockerfile seems to do the trick.

[polm]

Thanks for the reports everyone! I would say for the time being please downgrade click. We'll work on having a patch out for this soon if necessary, thought it looks like it might be addressed upstream.

[philgooch]

Adding click==8.0.4 at the end of my requirements.txt works for me. Alternatively, adding pip install click==8.0.4 within the Dockerfile after installing other dependencies also works.

[svlandeg]

• Upstream issue: ImportError: cannot import name 'get_terminal_size' from 'click.termui' fastapi/typer#377
• Upstream fix (to be released): Add click 8.1.0 support fastapi/typer#375

[svlandeg]

As the upstream issue is not fixed yet, we released v3.2.4 to deal with this issue.

[tiangolo]

Hello! I just released Typer 0.4.1, you can now upgrade the version and that should handle it. 🚀 🤓

[github-actions]

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.