poetry fails to parse apache-libcloud's python version specification

[deifactor]

• 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 11.6
• Poetry version: 1.2.0a2
• Link of a Gist with the contents of your pyproject.toml file: See below

Issue

Trying to lock the following pyproject.toml fails:

[tool.poetry]
name = "badver"
version = "0.1.0"
description = ""
authors = ["Ash <[email protected]>"]
readme = "README.md"

[tool.poetry.dependencies]
python = "^3.7"
apache-libcloud = "^3.1"


[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

The error message ultimately ends in

  Could not parse version constraint: >=3.5.*

  at ~/Library/Application Support/pypoetry/venv/lib/python3.7/site-packages/poetry/core/semver/helpers.py:140 in parse_single_constraint
      136│         try:
      137│             version = Version.parse(version)
      138│         except ValueError:
      139│             raise ValueError(
    → 140│                 "Could not parse version constraint: {}".format(constraint)
      141│             )
      142│
      143│         if op == "<":
      144│             return VersionRange(max=version)

and I think this is because of a line with python_requires=">=3.5.*, <4", in apache-libcloud's setup.py file.

I could try to git them to rephrase their dependencies, but I'd like to be able to install already-existing versions of packages.

This seems related to #3619.

[deifactor]

After looking into this, it looks like this is fixed in poetry-core, but that isn't in the latest version of poetry yet.

[finswimmer]

Hello @deifactor,

please don't call it a fix. :) See here why python-poetry/poetry-core#186 (comment)

Related discussion: #4176

Yes, the workaround is not included in the current preview release (1.2.0a2).

fin swimmer

[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.