`pip install rlms` on Python 3.10 silently installs broken v0.0.1a1 stub instead of failing

[samkorn]

Problem

The README quick-start says to run pip install rlms. On Python 3.10, this silently installs v0.0.1a1 — a stub package containing only a version string — instead of the real v0.1.0 release.

This happens because:

1. rlms v0.1.0 on PyPI has requires-python >= 3.11
2. The old v0.0.1a1 alpha has no Python version constraint
3. pip falls back to 0.0.1a1 without any warning, since it's the latest compatible version

The user then gets ModuleNotFoundError: No module named 'rlm' with no indication that they installed the wrong version.

Reproduction

$ python --version
Python 3.10.x

$ pip install rlms
# Silently installs 0.0.1a1

$ pip show rlms
Name: rlms
Version: 0.0.1a1
Summary: Python package.
Requires:
# No dependencies, no actual code

$ python -c "from rlm import RLM"
ModuleNotFoundError: No module named 'rlm'

v0.0.1a1 contents

The entire installed package is:

rlms/__init__.py  →  __version__ = '0.0.1a1'

No rlm/ module, no dependencies, no actual functionality.

Suggested fix

Consider yanking v0.0.1a1 from PyPI. It serves no purpose, and its existence causes pip to silently "succeed" on Python < 3.11 while installing nothing useful. After yanking, users on 3.10 would get a clear error:

ERROR: No matching distribution found for rlms

which is a much better experience than a silent broken install.

Alternatively, the README could note the Python >= 3.11 requirement more prominently next to the pip install instruction.

Environment

• Python 3.10
• pip 25.3
• macOS

[okhat]

Ah good issue, thanks @samkorn. We probably do want to support python 3.10 since end of life is still in October 2026.

This is probably a one-character pull request?