pythonexplosion/spaCy #11708Not a task: already works

Is it possible to loosen the upper-bound constraint on Typer?

envgap__explosion__spaCy-11708

Original GitHub issue ↗Dated source checkout ↗Opened 2022-10-27

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: d25f09468c4eca20eb464d78d35e439474ed2dbc
Manifest: requirements.txt
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

explosion/spaCy #11708 · read the original issue

Hi! I'd like to use spaCy in a project where I already used Typer v0.6.2. 



I cannot install spaCy because spaCy forces all Typer versions to be the following: 

https://github.com/explosion/spaCy/blob/865691d169c3be413007f0d7324e03a7aac3b3cb/requirements.txt#L12



I use Poetry as my dependency manager, which means that it will not allow the inclusion of spaCy as a dependency with the constraint, even if I do not want to use the CLI aspect of spaCy. 



Is there a reason for limiting Typer to <0.5.0, and is it possible to loosen this constraint? 



Thank you!

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]