mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-01 03:24:41 +01:00
92f10f2c34
So this was quite a journey: - We want relative depdendencies (using the `path` argument) whenever developing locally. Otherwise we would have to install each dependency every time we change a single character, which undoubtedly would cause us to waste time trying to debug an issue just because we forgot to install. - When publishing however we want to rely on the version number, since the repo context gets lost upon publishing, and path dependencies cause failures. The solution then it seems is to use `dev-dependencies` (not that surprising once you find it) with relative paths, so that `poetry install` uses these over the normal dependencies (no idea how they dedup them) and use `dependencies` when publishing. The paths are still in there when publishing, but `pip install` ignores them. I checked that `poetry install` from an unrelated project doesn't accidentally use the path dependencies, even when adding them as dev-dependencies. This should hopefully also allow installing them as a repo link, though I can't test that right now. |
||
|---|---|---|
| .. | ||
| docker | ||
| init | ||
| keys | ||
| libhsmd_python | ||
| msggen | ||
| plugins | ||
| pylightning | ||
| pyln-client | ||
| pyln-proto | ||
| pyln-spec | ||
| pyln-testing | ||
| reprobuild | ||
| sanitizer_suppressions | ||
| bootstrap-node.sh | ||
| lightning-cli.bash-completion | ||
| short_channel_id-to-txid.sh | ||
| startup_regtest.sh | ||