Wheels with tags in manylinux_x_y format cannot be resolved

Open
#199 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reproducing the failure with the requirement.txt entry for solace-pubsubplus==1.9.0 and the documented python-inspector command on Python 3.11/Linux. Trace how python-inspector handles the manylinux_x_y wheel tag during dependency resolution; done means the dependency resolves successfully and the reported ResolutionImpossible exception no longer occurs.

Written by the indexing model from the issue text.

Description

Hi,

I’m encountering an issue where the python-inspector tool does not resolve the wheel for a packages correctly if the wheel tag is in the format manylinux_x_y

Environment

Python Inspector Version: 0.12.0
Python Version: 3.11
Operating System: Linux, Ubuntu 22.04

Steps to Reproduce

Create a requirement.txt file with following content:

solace-pubsubplus==1.9.0 ; python_version >= "3.11" and python_version < "4.0"

Run the Python Inspector tool:

python-inspector -p 3.11 -o linux --json inspector_output.json --requirement requirement.txt

Observe the output.

Expected Behavior

The dependency can be resolved.

Actual Behavior

The tool throws an exception:

resolvelib.resolvers.exceptions.ResolutionImpossible: [RequirementInformation(requirement=<Requirement('solace-pubsubplus==1.9.0; python_version >= "3.11" and python_version < "4.0"')>, parent=None)]

Additional Information

Many thanks

Christoph

This issue arose while using ORT, which depends on python-inspector. It seems like the problem originates from python-inspector itself when analyzing requirements.txt.

Spec

https://github.com/pypa/manylinux

Dominant language
Python
Stars
23
Forks
29
Avg merge
1h 7m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/python-inspector

All issues in aboutcode-org/python-inspector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.