Metadata-Version: 2.4
Name: autofit
Version: 2026.7.29.1.post1
Summary: Tombstone release: autofit requires Python 3.12 or later.
License: MIT
Requires-Python: <3.12
Description-Content-Type: text/markdown
Dynamic: description
Dynamic: description-content-type
Dynamic: license
Dynamic: requires-python
Dynamic: summary

# autofit 2026.7.29.1.post1 — tombstone release

**This release contains no code and cannot be installed.** Installing it raises
an error telling you to upgrade Python.

`autofit` requires **Python 3.12 or later**. Releases at or below
`2026.7.29.1` were published declaring `Requires-Python >=3.9`, and PyPI
metadata is immutable, so they stay valid pip candidates forever. Without this
tombstone, `pip install autofit` on Python 3.9, 3.10 or 3.11 does not fail —
it silently backtracks to `2026.7.29.1` and installs a stack that is months
out of date and ships without JAX, with no warning at all.

This release sorts above `2026.7.29.1` and declares `Requires-Python
<3.12`, so it is the first thing pip finds below the floor and is
invisible at or above it. The result is a clear error instead of a quietly
stale install.

## What to do

Upgrade to Python 3.12 or later and reinstall:

```
python3.12 -m pip install autofit
```

To install a historical release deliberately, pin it exactly — that still
resolves on older Pythons:

```
pip install autofit==2026.7.29.1
```
