Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poetry 2.0 & [project] section #70

Open
alecandido opened this issue Jan 6, 2025 · 0 comments
Open

Poetry 2.0 & [project] section #70

alecandido opened this issue Jan 6, 2025 · 0 comments

Comments

@alecandido
Copy link
Member

In v2.0.0, Poetry started supporting PEP 621 (and especially PEP 631, that was merged in it), such that we can now specify projects' metadata in a tool-agnostic [project] table, and dependencies in the [project.dependencies] sub-table.

There are some subtleties, detailed in the migration guide, but I'm fairly convinced that all Qibo projects are completely unaffected, and we could perform a full migration.

Since the new Poetry version just came out, I'd recommend waiting a little before forcing the migration in all projects: marginally to ensure availability for everyone (though it is mainly distributed through PyPI, so already almost completely available), but mainly to avoid being among the first Guinea pigs...

After that, this will reduce our dependence on Poetry: I do not have any plan to dismiss it, but avoided locking to any specific tool is always a good thing, whenever achievable without major drawbacks (including developers' time).

@alecandido alecandido changed the title Poetry & PEP 621 Poetry & [project] section Jan 6, 2025
@alecandido alecandido changed the title Poetry & [project] section Poetry 2.0 & [project] section Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant