fix(parsing): handle None response.output in parse_response to preven…

[Vitaliy-Pikalo]

Fixes #3325

• I understand that this repository is auto-generated and my pull request may not be merged

Changes being requested

parse_response in src/openai/lib/_parsing/_responses.py iterates directly over response.output without guarding against None. When the Responses API returns a response with output=null (e.g. a content-filtered or empty response), this crashes with:

TypeError: 'NoneType' object is not iterable

Fix: Replace:

for output in response.output:

With:

for output in (response.output or []):

This makes the behavior safe when response.output is None, treating it as an empty list and returning an empty ParsedResponse.

Additional context & links

• Issue: parse_response crashes with TypeError when response.output is null in response.completed event (chatgpt.com Codex backend) #3325
• File: src/openai/lib/_parsing/_responses.py line 61
• Reproducible with any Responses API call where output is null

[marcuswood-oai]

Thank you for the contribution! The null-output parsing and stream recovery fix has landed in #3345, so I am closing this PR as superseded. We appreciate your help!