Hello,

How would I reproduce this conflict?

pip install -U llama-index-core fastapi ?

(that install above works fine for me in a fresh env)

I’ve got the issue when I’m using poetry/building my docker image, with pip install I simply get an error message

With that same install above? What python version?

I tried in a fresh google-colab and it installed without issue

I’m using python 3.10, I’ll send you the error message from a fresh env

When I install both at the same time in a fresh env there’s no problem, however I can’t seem to make it work with poetry

Because no versions of fastapi-cli match >0.0.2,<0.0.3

>0.0.3
and fastapi-cli (0.0.2) depends on typer (>=0.12.3), fastapi-cli (>=0.0.2,<0.0.3

>0.0.3) requires typer (>=0.12.3).        
    And because fastapi-cli (0.0.3) depends on typer (>=0.12.3), fastapi-cli (>=0.0.2) requires typer (>=0.12.3).
    Because no versions of fastapi match >0.111.0,<0.112.0
and fastapi (0.111.0) depends on fastapi-cli (>=0.0.2), fastapi (>=0.111.0,<0.112.0) requires fastapi-cli (>=0.0.2).
(1) Thus, fastapi (>=0.111.0,<0.112.0) requires typer (>=0.12.3).
 
    Because no versions of spacy match >3.7.1,<3.7.2

>3.7.2,<3.7.4

>3.7.4,<4.0.0
and spacy (3.7.1) depends on typer (>=0.3.0,<0.10.0), spacy (>=3.7.1,<3.7.2

>3.7.2,<3.7.4

>3.7.4,<4.0.0) requires typer (>=0.3.0,<0.10.0).
    And because spacy (3.7.2) depends on typer (>=0.3.0,<0.10.0)
and spacy (3.7.4) depends on typer (>=0.3.0,<0.10.0), spacy (>=3.7.1,<4.0.0) requires typer (>=0.3.0,<0.10.0).
    And because fastapi (>=0.111.0,<0.112.0) requires typer (>=0.12.3) (1), fastapi (>=0.111.0,<0.112.0) is incompatible with spacy (>=3.7.1,<4.0.0)
    And because llama-index-core (0.10.37.post1) depends on spacy (>=3.7.1,<4.0.0)
and no versions of llama-index-core match >0.10.37.post1,<0.11.0, fastapi (>=0.111.0,<0.112.0) is incompatible with llama-index-core (>=0.10.37.post1,<0.11.0).
    So, because somassistant-backend-llm-api depends on both llama-index-core (^0.10.37.post1) and fastapi (^0.111.0), version solving failed.

And same stuff with a docker image with a requirement.txt

hmm, lemme try with poetry

yea ok, got the same error. At the same time, super weird, because spacy is an optional dependency on core...

I can just mark that dependency as * in the next release

Yes please ! It would be perfect for me