vincenzopalazzo
/
rgb-cln
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
rgb-cln/contrib/pyln-client/pyln/client/__init__.py

20 lines
433 B
Python
Raw Normal View History

pyln: Bump the version of pyln-client
2019-12-11 18:39:52 +00:00
from .lightning import LightningRpc, RpcError, Millisatoshi
pyln: add RpcException for finer method failure control. Allows caller to set code and exact message to be returned. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: pyln-client: plugins can now raise RpcException for finer control over error returns.
2020-12-15 04:38:52 +00:00
from .plugin import Plugin, monkey_patch, RpcException
pyln-client/gossmap: add NodeId class. This is more efficient than converting them all to Pubkeys: about 3.8 seconds vs 5.4 seconds. Usually treating them as raw bytes is what we want anyway. [ Fixup by Michael Schmoock <michael@schmoock.net> ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-09-07 05:09:16 +01:00
from .gossmap import Gossmap, GossmapNode, GossmapChannel, GossmapNodeId
pyln: Bump the version of pyln-client
2019-12-11 18:39:52 +00:00
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 13:05:30 +01:00
__version__ = "0.12.1"
pyln: Bump the version of pyln-client
2019-12-11 18:39:52 +00:00
pyln: Split pylightning into multiple pyln modules This is the first step to transition to a better organized python module structure. Sadly we can't reuse the `pylightning` module as a namespace module since having importable things in the top level of the namespace is not allowed in any of the namespace variants [1], hence we just switch over to the `pyln` namespace. The code the was under `lightning` will now be reachable under `pyln.client` and we add the `pyln.proto` module for all the things that are independent of talking to lightningd and can be used for protocol testing. [1] https://packaging.python.org/guides/packaging-namespace-packages/ Signed-off-by: Christian Decker <decker.christian@gmail.com>
2019-07-23 14:26:28 +01:00
__all__ = [
"LightningRpc",
"Plugin",
"RpcError",
pyln: add RpcException for finer method failure control. Allows caller to set code and exact message to be returned. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: pyln-client: plugins can now raise RpcException for finer control over error returns.
2020-12-15 04:38:52 +00:00
"RpcException",
pyln: Split pylightning into multiple pyln modules This is the first step to transition to a better organized python module structure. Sadly we can't reuse the `pylightning` module as a namespace module since having importable things in the top level of the namespace is not allowed in any of the namespace variants [1], hence we just switch over to the `pyln` namespace. The code the was under `lightning` will now be reachable under `pyln.client` and we add the `pyln.proto` module for all the things that are independent of talking to lightningd and can be used for protocol testing. [1] https://packaging.python.org/guides/packaging-namespace-packages/ Signed-off-by: Christian Decker <decker.christian@gmail.com>
2019-07-23 14:26:28 +01:00
"Millisatoshi",
"__version__",
pyln.client: new functionality to access Gossmap. It doesn't do much work, but it does parse the gossmap file and extract nodes and channels. [ Fixup by Michael Schmoock <michael@schmoock.net> ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-09-07 05:09:15 +01:00
"monkey_patch",
"Gossmap",
pyln-client/gossmap: add NodeId class. This is more efficient than converting them all to Pubkeys: about 3.8 seconds vs 5.4 seconds. Usually treating them as raw bytes is what we want anyway. [ Fixup by Michael Schmoock <michael@schmoock.net> ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-09-07 05:09:16 +01:00
"GossmapNode",
"GossmapChannel",
"GossmapNodeId",
pyln: Split pylightning into multiple pyln modules This is the first step to transition to a better organized python module structure. Sadly we can't reuse the `pylightning` module as a namespace module since having importable things in the top level of the namespace is not allowed in any of the namespace variants [1], hence we just switch over to the `pyln` namespace. The code the was under `lightning` will now be reachable under `pyln.client` and we add the `pyln.proto` module for all the things that are independent of talking to lightningd and can be used for protocol testing. [1] https://packaging.python.org/guides/packaging-namespace-packages/ Signed-off-by: Christian Decker <decker.christian@gmail.com>
2019-07-23 14:26:28 +01:00
]