mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
833b7b4baa
core-lightning/contrib/pyln-client/pyproject.toml

26 lines
609 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-client, pyln-proto, pyln-testing: update to new versions. I actually did this manually to send 23.08 to Pypi a few days ago, as it's required for clnrest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-08-02 08:46:25 +02:00
version = "23.08"
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]
lightningd: updating python v3.7 to v3.8
2023-07-20 01:01:11 +02:00
python = "^3.8"
py: Update dependencies and relax constraints We were being very restrictive when describing the dependencies, so let's relax them a bit.
2023-06-16 13:46:33 +02:00
pyln-proto = ">=23"
pyln: Bump versions to v0.12.1 This is just before the introduction of `get_json_id`, but has the correct dependency constraints such that all packages can be updated to >=v0.12 and we don't mix minor versions.
2022-09-23 14:05:30 +02:00
pyln-bolt7 = ">=1.0"
pyln: Migrate pyln-client to PEP 517 (poetry)
2022-02-21 19:46:15 +01:00
[tool.poetry.dev-dependencies]
py: Update dependencies and relax constraints We were being very restrictive when describing the dependencies, so let's relax them a bit.
2023-06-16 13:46:33 +02:00
pytest = "^7"
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