Description
This repo uses the swagger-codegen, which is not actively maintained, at least from a my point of view. It makes lots of hacks like post-generation patching and it’s very hard to maintain these scripts.
For instance - here is a list of PRs which are ready to merge but are not merged yet and had to be applied as patches in Python generator:
- [python] remove imports from models swagger-api/swagger-codegen#7905 (Mar 25, waiting)
- [python] Avoid creating unused ThreadPools swagger-api/swagger-codegen#8061 (Apr 24, waiting)
- [python-asyncio] client supports _preload_content swagger-api/swagger-codegen#8204 (May 17, waiting)
- feat: support for python3.7 (async is a keyword) swagger-api/swagger-codegen#8401 (Jul 8, finally merged)
- fix: python/asyncio no-ssl-verify affects server certs only swagger-api/swagger-codegen#8797 (Oct 9, waiting)
A lot of contributors moved from the swagger-codegen to the new project - openapi-generator. Basically it’s a fork of swagger-codegen but it’s actively developed and it gains popularity very fast.
All above PRs are already ported and merged to the openapi-generator:
- [python] Avoid creating unused ThreadPools OpenAPITools/openapi-generator#1387 (merged)
- [python] asyncio supports _preload_content; remove unsed imports OpenAPITools/openapi-generator#107 (merged)
- Support for python 3.7 by renaming
asynctoasync_reqOpenAPITools/openapi-generator#519 (merged) - Bug fix: python/asyncio no-ssl-verify affects verification of server certs OpenAPITools/openapi-generator#1211 (merged)
What do you think about changing generator? Is it possible? I’ll be happy to work on it...