core-lightning/contrib/pyln-spec/bolt7/pyproject.toml

[tool.poetry]
name = "pyln-bolt7"
version = "1.0.4.246"
description = "BOLT7"
authors = ["Rusty Russell"]
license = "BSD-MIT"

packages = [
  { include = "pyln/spec/bolt7" },
]

[tool.poetry.dependencies]
python = "^3.8"

[tool.poetry.dev-dependencies]
pyln-proto = "^0.10.2"

[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
pyln: Migrate pyln-bolt7 to PEP517 (poetry) 2022-02-21 19:43:40 +01:00			`[tool.poetry]`
			`name = "pyln-bolt7"`
pyln-spec: update to latest spec. In particular, some field names have changed. lnprototest in master has already upgraded names, so this brings us into compatibility again. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Changed: pyln-spec: package updated to latest spec version. 2022-09-22 13:07:11 +09:30			`version = "1.0.4.246"`
pyln: Migrate pyln-bolt7 to PEP517 (poetry) 2022-02-21 19:43:40 +01:00			`description = "BOLT7"`
			`authors = ["Rusty Russell"]`
			`license = "BSD-MIT"`

			`packages = [`
			`{ include = "pyln/spec/bolt7" },`
			`]`

			`[tool.poetry.dependencies]`
lightningd: updating python v3.7 to v3.8 2023-07-19 16:01:11 -07:00			`python = "^3.8"`
pyln: Migrate pyln-bolt7 to PEP517 (poetry) 2022-02-21 19:43:40 +01:00
			`[tool.poetry.dev-dependencies]`
py: Disentangle pyln dependencies Turns out that the pyln-proto dependency in the bolt packages is only needed for testing, not for production. Making it a dev-dependency means it isn't considered in resolution anymore. Since the bolt, testing and client packages are to be used outside from the project we can't use relative dependencies either, so make then dependent on the version on PyPI. This also means we had to push a couple of updated to PyPI. Changelog-None 2022-03-15 10:58:38 +01:00			`pyln-proto = "^0.10.2"`
pyln: Migrate pyln-bolt7 to PEP517 (poetry) 2022-02-21 19:43:40 +01:00
			`[build-system]`
			`requires = ["poetry-core>=1.0.0"]`
			`build-backend = "poetry.core.masonry.api"`