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).
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).