-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[python] fix #23032 add sync httpx support #23044
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
146db3a
656de6a
f243adf
ea0fddd
fd1099c
672973a
7d352a9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -35,6 +35,7 @@ jobs: | |
| sample: | ||
| - samples/openapi3/client/petstore/python-aiohttp | ||
| - samples/openapi3/client/petstore/python-httpx | ||
| - samples/openapi3/client/petstore/python-httpx-sync | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P2: The new python-httpx-sync sample is included in the test matrix but missing from the pull_request path filters, so changes limited to that directory won’t trigger CI for this workflow. Prompt for AI agents |
||
| - samples/openapi3/client/petstore/python | ||
| - samples/openapi3/client/petstore/python-lazyImports | ||
| services: | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,15 @@ | ||||||
| generatorName: python | ||||||
| outputDir: samples/openapi3/client/petstore/python-httpx-sync | ||||||
| inputSpec: modules/openapi-generator/src/test/resources/3_0/python/petstore-with-fake-endpoints-models-for-testing.yaml | ||||||
| templateDir: modules/openapi-generator/src/main/resources/python | ||||||
| library: httpx-sync | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. instead of creating another library, what about an option called
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would be very impractical for mutiple threads to utilize same sync client if we make some kind of async to sync here. Each thread would need its own event loop. This leads to more issues if
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what if a client needs to call both sync and async methods in the same setting? they need to use 2 different Python SDKs?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i agree, it would be nice to have both sync and async clients in the same SDK to share models. But as separate classes
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. for some other clients in different programming languages, we already have both sync and async methods in the same API class with different method suffix. async method:
sync method:
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok. Shall i also create sync methods in
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i don't think so i think all you need is to create a sync version for each api method, which calls the corresponding async api method and wait for completion |
||||||
| additionalProperties: | ||||||
| packageName: petstore_api | ||||||
| mapNumberTo: float | ||||||
| poetry1: false | ||||||
| nameMappings: | ||||||
| _type: underscore_type | ||||||
| type_: type_with_underscore | ||||||
| modelNameMappings: | ||||||
| # The OpenAPI spec ApiResponse conflicts with the internal ApiResponse | ||||||
| ApiResponse: ModelApiResponse | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: The new python-httpx-sync sample is included in the test matrix but missing from the pull_request path filters, so changes limited to that directory won’t trigger CI for this workflow.
Prompt for AI agents