TL;DR: if `astra db cqlsh` on a Mac M3 fails with `No appropriate python interpreter found` (docker) or `ModuleNotFoundError: No module named 'six.moves'` (homebrew), the CLI downloads the cqlsh bundle into ~/.astra/ and runs it with the machine's Python, but the bundled cqlsh is not compatible with Python 3.12, the M3 default. Use an older Python: `brew install python@3.11` (after removing the 3.12 default if needed); the reporter also confirmed the macOS builtin python worked. In Astra CLI v1.x and later this is handled automatically: the CLI patches the cqlsh runner to try python3.11, python3.10, python3.9 before the default python3, so upgrading the CLI is the durable fix.

```text
No appropriate python interpreter found
ModuleNotFoundError: No module named 'six.moves'
```

## Steps

1. Upgrade the Astra CLI to v1.x+; or install python@3.11 via Homebrew.

2. Re-run `astra db cqlsh`.

   Expected: cqlsh starts. Success check: you get a cqlsh prompt.

## When to use this

- M3 Mac, Python 3.12 default, cqlsh bundle fails.

## When NOT to use this

- Other cqlsh errors; read the message.
- Non-M3 Macs with a compatible Python; it just works.

## Compatibility

- Astra CLI v1.x+ (auto-handles); manual python@3.11 for older CLIs.

## Variant phrasings

- "astra cqlsh M3 six.moves"
- "astra cli no appropriate python interpreter"

## Root cause

The bundled cqlsh predates Python 3.12 and breaks on its removed/renamed modules.

## Edge cases

- Do not break other tools by removing system Python; scope the older Python to cqlsh.