mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-12-28 17:44:47 +01:00
Code Issues Projects Releases Wiki Activity
0fd8a6492e
core-lightning/contrib/pyln-client/pyproject.toml

26 lines
614 B
TOML
Raw Normal View History

pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
[tool.poetry]
name = "pyln-client"
pyln: Fix relative path dependencies when publishing to PyPI 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.
2022-06-22 15:06:04 +02:00
version = "0.11.1"
doc: update c-lightning to Core Lightning almost everywhere. Mostly comments and docs: some places are actually paths, which I have avoided changing. We may migrate them slowly, particularly when they're user-visible. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-04-06 07:09:48 +02:00
description = "Client library and plugin library for Core Lightning"
pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
authors = ["Christian Decker <decker.christian@gmail.com>"]
license = "BSD-MIT"
py: Update the PyPI job to use poetry and correct versions Let's use poetry when we already use it for everything else. Changelog-None
2022-03-29 13:35:06 +02:00
readme = "README.md"
pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
packages = [
{ include = "pyln/client" },
]
[tool.poetry.dependencies]
python = "^3.7"
pyln: Update the makefile to use poetry for publishing
2022-04-25 14:38:41 +02:00
pyln-bolt7 = "^1.0"
pyln: Fix relative path dependencies when publishing to PyPI 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.
2022-06-22 15:06:04 +02:00
pyln-proto = "^0.11"
pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
[tool.poetry.dev-dependencies]
pytest = "^7.0.1"
pyln: Fix relative path dependencies when publishing to PyPI 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.
2022-06-22 15:06:04 +02:00
pyln-bolt7 = { path = "../pyln-spec/bolt7", develop = true }
pyln-proto = { path = "../pyln-proto", develop = true}
pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
Reference in New Issue Copy Permalink