[mikeysklar]

What

Docs only: several pools are allowed, and a pool can be created before connecting.

Why

Fixes #9481.

The pool object holds no state on any port.

A one-pool rule would only break working code.

Testing

claim	desktop lab	source, all ports with Python-visible pools
Two pools are separate and both work	yes	make_new always allocates
Pool created with radio off works later	yes	constructor only checks which interface
Pool works after reconnect	yes, weak test	pool has no fields to go stale
Pools share the socket limit	not shown	sockets are opened without using the pool
Access point mode can use a pool	not supported	httpserver_simpletest_manual_ap.py does it

Strict docs build passes. No hardware run.

AI assistance

Written with Claude Code, which ran the desktop lab tests and the docs build and read the port source.

🤖 Generated with Claude Code

[dhalbert]

This is fine. It's a convenience that there can be multiple pool objects, but it appears that there is no practical difference between them. I could imagine that different pools might be created locally in code so they don't have to be passed around or something.