I regenerated the client based on current master (which is on staging). This is now namespaced under threedi_api_client.openapi, as discussed. The old one is left in place (for backwards compatibility of the Api classes)
A further requirement of the new API is that the API_HOST setting must not include the version. It now works as follows:
intended usage: if you import V3Api from threedi_api_client.openapi and not include the version in API_HOST, all is fine, no warnings
legacy usage: if you import OrganisationsApi from openapi_client and include the version in API_HOST, all is fine, you only get some warnings
the other two combinations (importing from openapi_client and not specifying a version, or importing from threedi_api_client.openapi and specifying a version) fail silently and lead to 404 errors. I can't get around this because of the way it is implemented (partially autogenerated)
The asyncio openapi stuff is now namespaced under threedi_api_client.aio.openapi. I found it better than threedi_api_client.openapi.aio
I regenerated the client based on current master (which is on staging). This is now namespaced under
threedi_api_client.openapi, as discussed. The old one is left in place (for backwards compatibility of theApiclasses)A further requirement of the new API is that the API_HOST setting must not include the version. It now works as follows:
V3Apifromthreedi_api_client.openapiand not include the version in API_HOST, all is fine, no warningsOrganisationsApifromopenapi_clientand include the version in API_HOST, all is fine, you only get some warningsThe asyncio openapi stuff is now namespaced under
threedi_api_client.aio.openapi. I found it better thanthreedi_api_client.openapi.aio