Cyclic dependency between poetry and poetry-plugin-export

[maresb]

poetry-plugin-export v1.0.4 (and earlier) depends on poetry = "^1.2.0b1dev0".

Poetry 1.2.0b2 introduces a dependency on poetry-plugin-export = "^1.0.4".

While this might not be immediately problematic, ideally the directed dependencies graph should remain acyclic. This is already causing trouble in conda-forge/poetry-feedstock#67.

[xylar]

As I said in the conda PR, pip and pypi allow circular dependencies but conda does not. So a circular dependency would mean conda packages couldn't be built with the latest poetry.

[dimbleby]

While I agree with you that the cyclic dependency is undesirable, I think you've raised it in the wrong repository.

• The plugin definitely always needs to rely on poetry, no fix can be made here
• poetry relying on the plugin is I think the mistake. IIUC this is aimed at providing backwards compatibility for the poetry export command: but too bad!

[xylar]

@dimbleby, thanks very much for opening the PR in poetry.

[xylar]

Just a note to say that I think we can actually handle circular dependencies on conda-forge, it's just a bit awkward. If the circular dependencies can't be satisfied for either package with existing package builds, we have to do a build of one or the other package without the circular dependency and then another build with it. It's not elegant but it works. So we may be able to close this issue.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.