davide/palladum-lightning
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity
Files
ad040d0db865c89e4ec9aef28ff08c74a527ed68
palladum-lightning/pyproject.toml

67 lines
1.6 KiB
TOML
Raw Normal View History

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: Use poetry and PEP 517 locks for the root project Allows us to just rely on `poetry` to manage our dependencies, should finally solve all the `mrkd`, `mako` and `mistune` issues we've had for a while.
2022-02-22 14:33:41 +01:00
name = "cln-meta-project"
version = "0.1.0"
description = "Just a helper to get our python dependencies under control"
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 = "cdecker@blockstream.com" }]
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 = [
"Mako>=1.1.6",
"websocket-client>=1.2.3",
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
"grpcio-tools==1.75.1",
"grpcio==1.75.1",
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
# We want a specific version of protobuf to match CI's .github/scripts/setup.sh
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
"protobuf==6.32.1",
"cryptography>=46",
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
"pyln-client",
"pyln-proto",
"pyln-grpc-proto",
]
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
package-mode = false
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]
dev = [
# Test dependencies and inherited dependencies belong here
"crc32c>=2.2.post0", # Belongs to lnprototest
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
"pytest>=8.0.0",
"pytest-xdist>=3.6.0",
"pytest-test-groups>=1.2.0",
"pytest-timeout>=2.4.0",
"flake8>=7.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
"pytest-custom-exit-code==0.3.0",
"flaky>=3.7.0",
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
"requests>=2.32.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
"flask-socketio>=5",
]
pyln: Use poetry and PEP 517 locks for the root project Allows us to just rely on `poetry` to manage our dependencies, should finally solve all the `mrkd`, `mako` and `mistune` issues we've had for a while.
2022-02-22 14:33:41 +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
[project.optional-dependencies]
grpc = ["pyln-testing"]
pyln: Use poetry and PEP 517 locks for the root project Allows us to just rely on `poetry` to manage our dependencies, should finally solve all the `mrkd`, `mako` and `mistune` issues we've had for a while.
2022-02-22 14:33:41 +01:00
misc: Make the root project not a package
2025-09-01 11:43:35 +02:00
[tool.poetry]
package-mode = false
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.uv]
package = false
[tool.uv.workspace]
members = [
"contrib/pyln-client",
"contrib/pyln-proto",
"contrib/pyln-grpc-proto",
"plugins/wss-proxy",
"contrib/pyln-testing",
"contrib/pyln-spec/bolt1",
"contrib/pyln-spec/bolt2",
"contrib/pyln-spec/bolt4",
"contrib/pyln-spec/bolt7",
]
[tool.uv.sources]
pyln-client = { workspace = true }
pyln-proto = { workspace = true }
pyln-grpc-proto = { workspace = true }
wss-proxy = { workspace = true }
pyln-testing = { workspace = true }
pyln-bolt1 = { workspace = true }
pyln-bolt2 = { workspace = true }
pyln-bolt4 = { workspace = true }
pyln-bolt7 = { workspace = true }
Reference in New Issue Copy Permalink