"poetry install" (1.2.0) installs the wrong torch version in the first time on OSX

[chuanma]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: macOS Monterey (12.5.1)
• Poetry version: 1.2.0
• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/chuanma/6786dbf123a1b6ee8a22df2b16cb33a1

Issue

To reproduce this bug, first delete the poetry.lock if there is one. Then call poetry install twice. You will find that it fails in the first time, trying to install the wrong version (1.11.0+cpu) added for the linux platform. However, it works if you call poetry install again.

I guess that some cache was not removed after generating the poetry.lock file, and the cache caused the error, because it worked in the 2nd poetry install call.

➜  poetry install
...
Resolving dependencies... (0.9s)

Writing lock file

Package operations: 2 installs, 0 updates, 0 removals

  • Installing typing-extensions (4.3.0)
  • Installing torch (1.11.0+cpu): Failed

  RuntimeError

  Unable to find installation candidates for torch (1.11.0+cpu)

  at ~/Library/Application Support/pypoetry/venv/lib/python3.8/site-packages/poetry/installation/chooser.py:103 in choose_for
       99│
      100│             links.append(link)
      101│
      102│         if not links:
    → 103│             raise RuntimeError(f"Unable to find installation candidates for {package}")
      104│
      105│         # Get the best link
      106│         chosen = max(links, key=lambda link: self._sort_key(package, link))
      107│



➜  poetry install
Installing dependencies from lock file

Package operations: 1 install, 0 updates, 0 removals

  • Installing torch (1.11.0)

[dimbleby]

Basically the same as #6150

poetry solves for versions and markers, paying no attention to what distributions are available. I think that is unlikely to change. 1.11.0+cpu should be a satisfactory version wherever 1.11.0 is written.

It should be sheer luck that your install works sometimes but not others (I am mildly surprised that it varies).

As in #6150, you may be better off asking the pytorch project to use a consistent versioning scheme, it seems curious that they attach +cpu on linux and windows but not on mac.

[chuanma]

@dimbleby Agreed. I'll close this issue.

To help other people, some experiment results:

• In Poetry 1.2.0, it's consistent that separately calling poetry lock and poetry install works for me.
• In Poetry master branch (1.3.x), it always fails (trying to install 1.11.0+cpu on mac).

So if you are on 1.2.0, you may use this approach to temporarily avoid the issue.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.