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 export on CI #26

Open
itepifanio opened this issue Feb 5, 2025 · 0 comments
Open

Poetry export on CI #26

itepifanio opened this issue Feb 5, 2025 · 0 comments

Comments

@itepifanio
Copy link

itepifanio commented Feb 5, 2025

Hi @gerbenoostra thanks for the plugin, it works as described on the README.

I've been able to export the subrepositories correctly, but I was expecting been able to also create a root non-package pyproject.toml that points to the subrepositories and export them, which doesn't seem to work.

My idea was to create a global venv, export the root dependencies and install them, but the root export doesn't work it outputs my local paths in editable mode.

This is my current setup, the package A doesn't use the plugin, but the package B (that depends on A) uses the plugin.

── pyproject.toml
└── repo
    ├── A
    │   └── pyproject.toml
    └── B
        └── pyproject.toml

My root pyproject.toml is a non package that points to the subrepositories, but exporting from the root doesn't export the package a and b with their actual versions.

...

[tool.poetry]
package-mode = false

[tool.poetry.dependencies]
python = ">=3.11"
package-a = { path = "A", develop = true }
package-b = { path = "B", develop = true }

[tool.poetry-monorepo.deps]

Edit: This is a non-blocking issue, is more something that I would expected it would work

@itepifanio itepifanio changed the title Poetry export on the root Poetry export on CI Feb 5, 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