requests: stream parameter is noop

MicroPython v1.21.0; Raspberry Pi Pico W with RP2040.

requests.request exposes a stream=None parameter:

https://github.com/micropython/micropython-lib/blob/d8e163bb5f3ef45e71e145c27bc4f207beaad70f/python-ecosys/requests/requests/__init__.py#L36-L46

but it is never functionally used, nor is some iter_content API exposed; the parameter is only forwarded to recursive request calls.

Workaround:

r = requests.get(...)
# sidestep @property content, which just reads socket data into memory until EOF
s = r.raw
r.raw = None
buf = bytearray(1024)
while s.readinto(buf) > 0:
    # handle data in buf (e.g. write to file)

if the above is implemented into some iter_content, is the stream parameter even needed? Am I missing something?

Start in python-ecosys/requests/requests/init.py at the request function linked in the issue, then trace how stream is forwarded and how response.content and response.raw consume the socket. Reproduce the current behavior on the stated MicroPython and Raspberry Pi Pico W setup; done means the intended streaming behavior is established and stream or its replacement has a consistent, usable API.