poetry: support for poetry metadata format 2.0

[GabMus]

No description provided.

[mig5]

Thank you for this! I applied this as a patch and it has solved the problem for me when running flatpak-poetry-generator.py against my poetry.lock after I upgraded poetry to version 1.5.0.

[ENDrain]

LGTM. Maybe could also add a line in README.md listing metadata formats supported, but not sure if that's necessary. @mig5, since this worked for you could you also please add an approving review?

[GabMus]

I really think we should merge this

[d4nj1]

Would also be nice if the --yaml output format could be added similar to

https://github.com/flatpak/flatpak-builder-tools/blob/master/pip/flatpak-pip-generator#L55-L67
with
https://github.com/flatpak/flatpak-builder-tools/blob/master/pip/flatpak-pip-generator#L480-L491

[hfiguiere]

Can you rebase this? We could get it merged eventually.

[uninstall-your-browser]

--production does not seem to work, it still tries (and fails) to retrieve dev dependencies (unless I'm somehow generating my lock file wrong?). Though it should probably be changed to --without <group-name>, since poetry has deprecated --no-dev.

[hfiguiere]

@GabMus unless this gets rebased, this can't be merged.

[GabMus]

rebased, note that this PR is ancient and I don't even use flatpak-builder-tools anymore, so make sure this works as expected before merging

[bbhtt]

I'll try to review and merge this in the next weeks. It would have been nice if the lock file format was documented but according to https://github.com/orgs/python-poetry/discussions/6763 it's not.

In the meantime, flatpak-pip-generator now supports parsing pyproject.toml and Poetry v2 supports PEP 621 metadata. So flatpak-pip-generator can be used directly instead of operating on the lock file.

[bbhtt]

Would also be nice if the --yaml output format could be added similar to

This should be a separate issue. You just include the generated manifest. Having multiple formats is not a top priority.

--production does not seem to work, it still tries (and fails) to retrieve dev dependencies

--production should work now for v2 metadata.

Though it should probably be changed to --without <group-name>, since poetry has deprecated --no-dev.

Indeed, generic group support can be done later. This can be a separate issue. For now --production excludes things that have only dev in their groups.

[bbhtt]

Tested this on a v1 and v2 lock files with the --production combination. Seems to work.

poetryv2.txt
poetryv1.txt