swagger-api / swagger-api/swagger-codegen
[Python] Lazy initialisation of thread pool in client
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Swagger-codegen version
Version 3.0.27.
Python client generation (both urlliib3 and asyncio)
Swagger declaration file content or url
Any swagger content.
Command line used for generation
java -jar swagger-codegen.jar -i -l python [--library asyncio]
Steps to reproduce
Related issues/PRs
Suggest a fix/enhancement
This was fixed in swagger codegen 2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Python client generation command in the issue and compare urllib3 and asyncio output with swagger-codegen 2, where the issue says this was fixed. Trace the generated client templates or entry points for thread-pool setup. Done means both Python client variants initialize their thread pools lazily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100