Skip to content

ERROR: No matching distribution found for pymsalruntime==0.17.1 #31007

@lilz-egoto

Description

@lilz-egoto

Describe the bug

I get this error on azure CI when trying to use the latest azure cli through python. Python version 3.11.9

ERROR: Could not find a version that satisfies the requirement pymsalruntime==0.17.1 (from versions: 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.11.2, 0.12.4, 0.13.0, 0.13.1, 0.13.2, 0.13.9, 0.13.12, 0.14.0, 0.14.2a1, 0.14.2, 0.15.0a1, 0.18.0)
ERROR: No matching distribution found for pymsalruntime==0.17.1

Related command

ERROR: Could not find a version that satisfies the requirement pymsalruntime==0.17.1 (from versions: 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.11.2, 0.12.4, 0.13.0, 0.13.1, 0.13.2, 0.13.9, 0.13.12, 0.14.0, 0.14.2a1, 0.14.2, 0.15.0a1, 0.18.0)
ERROR: No matching distribution found for pymsalruntime==0.17.1

Errors

ERROR: Could not find a version that satisfies the requirement pymsalruntime==0.17.1 (from versions: 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.11.2, 0.12.4, 0.13.0, 0.13.1, 0.13.2, 0.13.9, 0.13.12, 0.14.0, 0.14.2a1, 0.14.2, 0.15.0a1, 0.18.0)
ERROR: No matching distribution found for pymsalruntime==0.17.1

Issue script & Debug output

ERROR: Could not find a version that satisfies the requirement pymsalruntime==0.17.1 (from versions: 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.11.2, 0.12.4, 0.13.0, 0.13.1, 0.13.2, 0.13.9, 0.13.12, 0.14.0, 0.14.2a1, 0.14.2, 0.15.0a1, 0.18.0)
ERROR: No matching distribution found for pymsalruntime==0.17.1

Expected behavior

The pymsalruntime should exist according to pypi.

Environment Summary

n/a

Additional context

No response

Metadata

Metadata

Assignees

Labels

Azure CLI TeamThe command of the issue is owned by Azure CLI teamcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions