Packages not discoverable by pip

[LeonardoEmili]

Description

Good evening,
I am facing this issue that prevents me from installing specific package versions even though they are present in the PyPi repository. In my case, running pip3 install torchtext==0.9.1 produces the following error:

ERROR: Could not find a version that satisfies the requirement torchtext==0.9.1 (from versions: 0.1.1, 0.2.0, 0.2.1, 0.2.3, 0.3.1, 0.4.0, 0.5.0, 0.6.0, 0.10.0)
ERROR: No matching distribution found for torchtext==0.9.1

Running pip3 index versions torchtext seems that some versions are missing (even though they should be):

torchtext (0.10.0)
Available versions: 0.10.0, 0.6.0, 0.5.0, 0.4.0, 0.3.1, 0.2.3, 0.2.1, 0.2.0, 0.1.1

More
Creating a conda environment with the same Python (3.9.7) and pip3 (pip 21.2.4 from /opt/homebrew/Caskroom/miniconda/base/envs/prova/lib/python3.9/site-packages/pip (python 3.9)) versions and then running the same command produces the correct version list:

torchtext (0.10.1)
Available versions: 0.10.1, 0.10.0, 0.9.1, 0.9.0, 0.8.1, 0.6.0, 0.5.0, 0.4.0, 0.3.1, 0.2.3, 0.2.1, 0.2.0, 0.1.1

Any clue of what could be the issue with the base pip3 installation?

Expected behavior

The complete list of versions for a given package in the first case.

pip version

pip 21.2.4 from /opt/homebrew/lib/python3.9/site-packages/pip (python 3.9)

Python version

Python 3.9.7

OS

macOS Big Sur 11.6 (Apple Silicon)

How to Reproduce

1. pip3 index versions torchtext

Output

No response

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[uranusjr]

torchtext 0.9.1 does not publish either its source code or an M1 binary, so it "exists" but does not "exist" for you.

Merging this into #10052.

[LeonardoEmili]

torchtext 0.9.1 does not publish either its source code or an M1 binary, so it "exists" but does not "exist" for you.

Merging this into #10052.

Thanks for your clarification @uranusjr . What about the more section, how is it possible that I get it working when running in a ad-hoc conda environment with the same pip and python versions?

[uranusjr]

One possibility is the Conda Python is running on Rosetta and is therefore fetching x86_64 images instead. There are a lof of possibilities.

[LeonardoEmili]

One possibility is the Conda Python is running on Rosetta and is therefore fetching x86_64 images instead. There are a lof of possibilities.

That's true! It seems that with that option conda creates an environment running on Rosetta, enabling pip to find all the package versions. Thanks for your time @uranusjr , have a good day!