lightning

8679 Commits

55 Branches

107 Tags

38 MiB

Tree: e13c435aca

Commit Graph

Author	SHA1	Message	Date
Christian Decker	6c19818314	pyln-proto: Add invoice utilities We are about to disect a couple of invoices for features, so let's add a class that can encode and decode invoices from bolt11 strings. This is pretty much the lnaddr.py file created by @rustyrussell with some minor changes. I'm planning to clean this up further which is why I'm only exporting the `Invoice` class for now.	5 years ago
Christian Decker	d3f6ebf911	pyln-proto: Added a couple of utilities to manage onions and zbase32	5 years ago
Christian Decker	3418e59d76	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>	6 years ago

Author

SHA1

Message

Date

Christian Decker

6c19818314

pyln-proto: Add invoice utilities

We are about to disect a couple of invoices for features, so let's add a class
that can encode and decode invoices from bolt11 strings. This is pretty much
the lnaddr.py file created by @rustyrussell with some minor changes. I'm
planning to clean this up further which is why I'm only exporting the
`Invoice` class for now.

5 years ago

Christian Decker

d3f6ebf911

pyln-proto: Added a couple of utilities to manage onions and zbase32

5 years ago

Christian Decker

3418e59d76

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>

6 years ago

53 Commits (e13c435acaa82ded2654a6d1aed7b9289d5b7dcf)