Skip to content

Cannot load generated modules when output folder does not match clientNamespaceName #2293

@darrelmiller

Description

@darrelmiller

In the Moostodon sample, I generated code in the "sdk" folder but the clientNamespaceName was "MastodonClientLib". This prevented lazy imports from working as it was looking for modules in "mastodon_client_lib". Once I renamed the "sdk" folder to mastodon_client_lib the error went away.

We should probably make clientNamespaceName be unused for Python and rely only on the output folder name.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done ✔️

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions