Dependencies Issue

01 / FAILURE SIGNATURE

Captured in a clean container

ERROR: Cannot install basic-pitch==0.0.1, basic-pitch==0.1.0 and basic-pitch==0.2.0 because these package versions have conflicting dependencies.

02 / ENVIRONMENT RECIPE

Base commit

53cde930eeb1ffbda41b09afeb90fbd9f01ec8bd

Manifest

setup.cfg

Reproduce

python3 -m pip install --no-build-isolation .

Run under trace

python3 -c "import importlib; m=importlib.import_module('basic_pitch'); print(getattr(m,'__version__','ok'))"

03 / ORIGINAL ISSUE TEXT

Hi everybody!

I'm super curious to try basic-pitch, but I don't get past the pip installation process. Do you have any idea what could be the cause of this problem?



  Preparing metadata (pyproject.toml) ... done

ERROR: Cannot install basic-pitch==0.0.1, basic-pitch==0.1.0 and basic-pitch==0.2.0 because these package versions have conflicting dependencies.



The conflict is caused by:

    basic-pitch 0.2.0 depends on tensorflow<2.10 and >=2.4.1

    basic-pitch 0.1.0 depends on tensorflow<2.7.0 and >=2.4.1

    basic-pitch 0.0.1 depends on tensorflow<2.7.0 and >=2.4.1



To fix this you could try to:

1. loosen the range of package versions you've specified

2. remove package versions to allow pip attempt to solve the dependency conflict



ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

04 / LABELS

Labels checked by running the task · needs human review

[]

Historical install-only results are not EnvGap validation.

Default recipe; commands are ecosystem conventions, not issue-specific.

Proposed by batch curation; baseline wall 105s

Preparation uses current registries. Historical package availability is not enforced here; execution metadata records this limitation separately from the oracle's date-bounding policy.

manifest_path repointed from pyproject.toml (build-system only, no [project] dependencies) to setup.cfg, which carries install_requires; eval parses D1 from this file.