model-card-toolkit icon indicating copy to clipboard operation
model-card-toolkit copied to clipboard

Unable to pip install model-card-toolkit in Python 3.10 notebook

Open astockley opened this issue 4 months ago • 1 comments

What happened?

When trying to pip install "model-card-toolkit>=1.0.0" in a Python 3.10 terminal, I ran into dependency conflicts even in a brand new virtual environment. I cannot find anywhere in your documentation that this package is incompatible with Python 3.10, and was wondering if this is intentional/if there are plans to release a new version of this package that is compatible with this python version. I also tried with "model-card-toolkit==2.0.0" and had the same issue.

What is the expected behavior?

I was expecting to be able to pip install and use this package in a v3.10 environment. (I currently have this working in Python 3.9 but am going through a Python upgrade.)

How can we reproduce the problem?

I ran into this problem in my python 3.10 terminal (running in a GCP user-managed notebook) with a brand new venv, running exactly the pip install commands described in the docs here

I.e.:

pip install --upgrade pip pip install 'model-card-toolkit>=1.0.0'

Model Card Toolkit Version

=1.0.0

Python Version

3.10

Platforms

GCP user-managed notebook

Relevant log output

ERROR: Cannot install model-card-toolkit==1.0.0, model-card-toolkit==1.1.0, model-card-toolkit==1.2.0, model-card-toolkit==1.3.0, model-card-toolkit==1.3.1 and model-card-toolkit==1.3.2 because these package versions have conflicting dependencies.

The conflict is caused by:
    model-card-toolkit 1.3.2 depends on ml-metadata<1.6.0 and >=1.5.0
    model-card-toolkit 1.3.1 depends on ml-metadata<1.6.0 and >=1.5.0
    model-card-toolkit 1.3.0 depends on ml-metadata<1.6.0 and >=1.5.0
    model-card-toolkit 1.2.0 depends on ml-metadata<1.6.0 and >=1.5.0
    model-card-toolkit 1.1.0 depends on ml-metadata<1.3.0 and >=1.2.0
    model-card-toolkit 1.0.0 depends on ml-metadata<0.27.0 and >=0.26.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

astockley avatar Feb 27 '24 10:02 astockley

Any updates? Still not found a work around for this.

astockley avatar Mar 21 '24 08:03 astockley