3 Commits

Author	SHA1	Message	Date
Jarret Dyrbye	d712f732d8	pylightning - allow unicode symbols in the description to be passed as-is to the daemon ... addresses issue #2753. Formatting the JSON with the default parameters will escape the unicode symbols in a way that c-lightning won't allow, leading to an exception. Changelog-Fixed: `pylightning` now handles unicode characters in JSON-RPC requests and responses correctly.	2019-11-29 21:38:17 +01:00
Christian Decker	81f7978cc8	pyln: Migrate implementation from pylightning to pyln-client ... This should not affect any consumer of the API since we just shift the actual implementation from one side to the other, and keep aliases in place so scripts don't break. We also bump the version number from 0.0.7.3 to 0.7.4 which allows us to be in sync with c-lightning itself, and remove the superfluous `0` in front.	2019-11-12 21:23:55 +01:00
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>	2019-09-30 13:27:37 +02:00