pip fails to find new package version even though it is available on PyPI website

Environment

• pip version: 19.0.3
• Python version: 3.7.3
• OS: macOS 10.15.5
• twine version 3.1.1 (pkginfo: 1.5.0.1, requests: 2.20.1, setuptools: 40.8.0, requests-toolbelt: 0.9.1, tqdm: 4.46.1)

Description I can see the latest version (0.2.1) of my package here – https://pypi.org/project/django-eb-sqs-worker/

But when I try to install it I get the following:

% pip3 install django-eb-sqs-worker==0.2.1  
Collecting django-eb-sqs-worker==0.2.1
  Could not find a version that satisfies the requirement django-eb-sqs-worker==0.2.1 (from versions: 0.1.0)
No matching distribution found for django-eb-sqs-worker==0.2.1

If i don’t specify the version it installs 0.1.0:

% pip3 install django-eb-sqs-worker       
Collecting django-eb-sqs-worker
Installing collected packages: django-eb-sqs-worker
Successfully installed django-eb-sqs-worker-0.1.0

Upgrading also does not work:

% pip3 install --upgrade django-eb-sqs-worker
Requirement already up-to-date: django-eb-sqs-worker in ./.venv/lib/python3.7/site-packages (0.1.0)

Interestingly, the search results show 0.2.1 as the latest version:

% pip3 search django-eb-sqs-worker   
django-eb-sqs (1.38)                              - A simple task manager for AWS SQS
django-eb-sqs-worker (0.2.1)                      - Django Background Tasks for Amazon Elastic Beanstalk
  INSTALLED: 0.1.0
  LATEST:    0.2.1
sqs-workers (0.5.2)                               - SQS Workers

Expected behavior I expect the latest version of the package be available via pip install (0.2.1 in this case)

What I’ve tried

1. First I’ve uploaded the new version of the package using twine which led to the problem described here
2. I’ve tried the “purge” solution described in #4888 with both https://pypi.python.org/simple/<package-name> and https://pypi.org/simple/<package-name>/ instead. addresses, but that didn’t resolve the issue
3. I’ve waited around 12 hours to make sure the index and cache updates, but that did not seem to help

[McSinyx]

Hi @DataGreed, probably you made some mistake/typo during the build of 0.2.1—0.2.2 is looking good now. One alternative to setuptools is flit, which you might want to consider to avoid having to handle everything explicitly—flit publish will take care of setuptools’ and twine’s job in one go. Either way, I believe that this issue is solved and could be closed now.

^{This again proves my point that twine upload dist/* is confusing for new-comers in Python packaging ecosystem, regarding which file is to be uploaded.}

[uranusjr]

I believe pip has dropped support to eggs for a while now. You’ll need to publish in sdist (tar.gz) or wheel (whl) now.