[BUG] Cannot install fiftyone with poetry because of kaleido dependency

[ClementPinard]

System information

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
• Python version (python --version):
• FiftyOne version (fiftyone --version):
• FiftyOne installed from (pip or source): poetry (https://python-poetry.org/)

Commands to reproduce

Create an empty poetry project, and just try to add fiftyone to the project with poetry add fiftyone

poetry init
poetry add fiftyone

The installation will fail with the following error message :

  • Updating kaleido (0.2.1 -> 0.2.1.post1): Failed

  RuntimeError

  Unable to find installation candidates for kaleido (0.2.1.post1)

  at ~/.local/share/pypoetry/venv/lib/python3.10/site-packages/poetry/installation/chooser.py:76 in choose_for
       72│ 
       73│             links.append(link)
       74│ 
       75│         if not links:
    →  76│             raise RuntimeError(f"Unable to find installation candidates for {package}")
       77│ 
       78│         # Get the best link
       79│         chosen = max(links, key=lambda link: self._sort_key(package, link))

Describe the problem

You will get the exact same error message if you do poetry add kaleido : poetry gets the latest version available, i.e. 0.2.1.post1 and tries to install it.

The problem resides in the fact that kaleido 0.2.1.post1 only exists for arm processors. I don't know exactly why, but it makes it impossible to install it with poetry, while pip simply ignore this version and install 0.2.1 instead.

The easy fix for this is to pin the version to 0.2.1 instead of any version (which leads to 0.2.1.post1 for the moment)

See related issue : plotly/Kaleido#156

What areas of FiftyOne does this bug affect?

• App: FiftyOne application issue
• Core: Core Python library issue
• Server: FiftyOne server issue

Willingness to contribute

The FiftyOne Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the FiftyOne codebase?

• Yes. I can contribute a fix for this bug independently
• Yes. I would be willing to contribute a fix for this bug with guidance from the FiftyOne community
• No. I cannot contribute a bug fix at this time