[Modelina] Add support for Python 3.x

[avineshwar]

Reason/Context

Please try answering few of those questions

• Why we need this improvement?
• How will this change help?
• What is the motivation?

Description

Please try answering few of those questions

• What changes have to be introduced?
• Will this be a breaking change?
• How could it be implemented/designed?

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jonaslagoni]

@avineshwar have you checked out the next version?

If you have, do you mind clarifying how the current python output is insufficient to your liking?

[zaytsevand]

I guess it's about Implicit-related imports which will not work with Python 3.3+:
PEP-328
Changed in version 3.3

[jonaslagoni]

That should be manageable, we also have different import ways for TypeScript.

[zaytsevand]

That should be manageable, we also have different import ways for TypeScript.

Could you please suggest a proper way to implement an import differently?
My dumb workaround for the issue is:

const models = await generator.generateCompleteModels(spec, {});
const libraryDependencies = new Set(models.flatMap(m => m.dependencies));

for (const model of models) {
    await writeFile(`${outputDirectory}/${model.modelName}.py`,
        model.result
            .split('\n')
            .map(s => {
                if (libraryDependencies.has(s)) {
                    return s;
                }
                if (s.startsWith('from ')) {
                    return s.replace('from ', 'from .');
                }
                return s;
            })
            .map(s => `${s}\n`)
            .filter(s => s !== '\n'));
}

1. If it's a library dep, skip it altogether. Unfortunately, here I'm working with dependencies on an import statement level, not with package names (which would be a much cleaner alternative)
2. If it's any other import, then prefix it with a dot, assuming that here we won't receive anything but local imports

[jonaslagoni]

If the generateCompleteModels function does not generate accurate imports, then we should change how it renders dependencies.

Do you have a suggestion for an option you can provide with the function? That we can use inside the python renderer to render appropriate dependencies?

[zaytsevand]

@jonaslagoni please check the attached PR. Hope that it would do the trick #981

[jonaslagoni]

I am gonna close this issue for now as a fix is in place.

Feel free to reopen @avineshwar if you don't find it solved it.