mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-22 22:45:27 +01:00
6583f0dead
Having the grpc bindings in the pyln-testing package was always a bit strange, however it came with additional issues. Due to the way that protos are handled by protobuf, any name clash, independently of where we import the protos, would cause an import error. This usually happens in diamond-pattern dependencies, and so pull out the generated files into their own package that everyone else can rely on. Changelog-None |
||
|---|---|---|
| .. | ||
| docker | ||
| init | ||
| keys | ||
| msggen | ||
| plugins | ||
| pylightning | ||
| pyln-client | ||
| pyln-grpc-proto | ||
| pyln-proto | ||
| pyln-spec | ||
| pyln-testing | ||
| reprobuild | ||
| sanitizer_suppressions | ||
| bootstrap-node.sh | ||
| clang-coverage-report.sh | ||
| config-example | ||
| giantnode.py | ||
| lightning-cli.bash-completion | ||
| short_channel_id-to-txid.sh | ||
| startup_regtest.sh | ||