[BUG] [Python] - license format

[Huluti]

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?

Description

pyproject.toml file had a format change.

Previous:
licence: "MIT"

Now:
license = { text = "MIT" }

Source: https://python-poetry.org/docs/pyproject/#license

Not following this change leads to this error when trying to upload the package generated to PyPi:

ERROR    InvalidDistribution: Invalid distribution metadata: unrecognized or    
         malformed field 'license-expression' 

Also, I did not find a way to change the license used by setting a var in config file.

openapi-generator version

7.14.0

Suggest a fix

Use this new format in pyproject.mustache file.

[wing328]

thanks for reporting the issue

do you mind filing a pr with the suggested fix?

[keepConcentration]

@Huluti @wing328

Do you mind if I take this issue and open a PR?

[wing328]

@keepConcentration yes please 🙏

[keepConcentration]

@wing328 Hi!

I’ve noticed that for the standard python generator, we have the poetry1 configuration flag available, which enables conditional formatting of pyproject.toml—for example, switching between:

license = "{{license}}"

and the newer:

license = { text = "{{license}}" }

depending on whether poetry1=true.

However, when using the python-pydantic-v1 generator, this poetry1 flag (and therefore the conditional license formatting logic) is not currently supported. As a result, we can't apply the same dynamic license formatting logic in its templates.

I’d appreciate any guidance from maintainers or contributors on the preferred direction for handling this in python-pydantic-v1, so we can ensure consistency while avoiding unnecessary disruption. Thanks!

[artem-ilin]

I also came across this issue. Maybe it's a good idea to get rid of boolean poetry1 and replace it with packageManager=poetry and packageManagerVersion=2 (or 1). Just keeping in mind that there are some other package managers (pdm, uv) and we might see their implementation in future.

[dsteeley]

I've hit this issue and would like to help get it resolved. @wing328 are you able to provide any guidance on this issue for how it should be handled in the python-pydantic-v1 generator and whether the poetry1 boolean should be replaced as per @artem-ilin comment.

[wing328]

@keepConcentration can you please file a PR with the fix for python generator to start with?

for python-pydantic-v1, we will address it with another PR instead assuming there's a demand to fix the same issue in the python-pydantic-v1 (which will be sunset eventually as users should be using pydantic v2 in the python client generator instead)