contrib/pyln-client/pyproject.toml

[project]
name = "pyln-client"
version = "25.12rc1"
description = "Client library and plugin library for Core Lightning"
authors = [{ name = "Christian Decker", email = "decker.christian@gmail.com" }]
license = { text = "BSD-MIT" }
readme = "README.md"
requires-python = ">=3.9,<4.0"
dependencies = ["pyln-proto>=23", "pyln-bolt7>=1.0"]

[dependency-groups]
dev = ["pytest>=8.0.0", "pyln-bolt7", "pyln-proto"]

[tool.hatch.build.targets.wheel]
packages = ["pyln"]

[build-system]
requires = ["hatchling>=1.0.0"]
build-backend = "hatchling.build"
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`[project]`
pyln: Migrate pyln-client to PEP 517 (poetry) 2022-02-21 19:46:15 +01:00			`name = "pyln-client"`
change log for 25.12rc1 2025-11-21 03:54:39 +00:00			`version = "25.12rc1"`
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 14:39:48 +09:30			`description = "Client library and plugin library for Core Lightning"`
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`authors = [{ name = "Christian Decker", email = "decker.christian@gmail.com" }]`
			`license = { text = "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"`
chore: Update python dependencies I got a bit annoyed by all the "your protobuf gencode is too old" warnings in downstream packages, so I spent a bit of time updating any stale dependency and now we're back allowing packages up to the latest release. That should maximize the compatibility, and allow downstream packages to chose their own versions, as long as they are compatible (semantic versioning). 2025-09-29 16:54:25 +02:00			`requires-python = ">=3.9,<4.0"`
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`dependencies = ["pyln-proto>=23", "pyln-bolt7>=1.0"]`
pyln: Migrate pyln-client to PEP 517 (poetry) 2022-02-21 19:46:15 +01:00
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`[dependency-groups]`
chore: Update python dependencies I got a bit annoyed by all the "your protobuf gencode is too old" warnings in downstream packages, so I spent a bit of time updating any stale dependency and now we're back allowing packages up to the latest release. That should maximize the compatibility, and allow downstream packages to chose their own versions, as long as they are compatible (semantic versioning). 2025-09-29 16:54:25 +02:00			`dev = ["pytest>=8.0.0", "pyln-bolt7", "pyln-proto"]`
pyln: Migrate pyln-client to PEP 517 (poetry) 2022-02-21 19:46:15 +01:00
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`[tool.hatch.build.targets.wheel]`
			`packages = ["pyln"]`
pyln: Migrate pyln-client to PEP 517 (poetry) 2022-02-21 19:46:15 +01:00
			`[build-system]`
refactor: pyproject.toml poetry to uv + hatch make use of standard keys for project and dependeny specification - provide sources to run uv build so that it can refer local packages - using hatchling for build as is stock build option - use optional-dependencies.dev for dev-dependencies - add hatch targets for packages and includes where unclear Changelog-Update: use uv with hatchling instead of poetry 2025-08-03 08:01:06 +05:30			`requires = ["hatchling>=1.0.0"]`
			`build-backend = "hatchling.build"`