fix(openai): don't eagerly import types from openai as they may not be available #2601

nirga · 2025-02-04T10:22:37Z

I have added tests that cover my changes.
If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
(If applicable) I have updated the documentation accordingly.

…e available

fix(openai): don't eagerly import types from openai as they may not b…

ad416ae

…e available

dosubot bot added size:S This PR changes 10-29 lines, ignoring generated files. bug Something isn't working python Pull requests that update Python code labels Feb 4, 2025

nirga changed the title ~~fix(openai): don't eagerly import types from openai as they may not b…~~ fix(openai): don't eagerly import types from openai as they may not be available Feb 4, 2025

OzBenSimhonTraceloop approved these changes Feb 4, 2025

View reviewed changes

nirga merged commit 09a9d04 into main Feb 4, 2025
9 checks passed

nirga deleted the fix-openai-v0-compat branch February 4, 2025 10:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(openai): don't eagerly import types from openai as they may not be available #2601

fix(openai): don't eagerly import types from openai as they may not be available #2601

nirga commented Feb 4, 2025 •

edited

Loading

fix(openai): don't eagerly import types from openai as they may not be available #2601

fix(openai): don't eagerly import types from openai as they may not be available #2601

Conversation

nirga commented Feb 4, 2025 • edited Loading

nirga commented Feb 4, 2025 •

edited

Loading