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

44 lines
1.3 KiB
Python
Raw Normal View History

pyln: Pin mypy to version 0.790 since later has import path issues
2021-03-19 15:19:01 +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
from setuptools import setup
pyln: Change the setup.py file not to import the package This would lead to errors about missing dependencies when attempting to install using `pyhon setup.py install`. This is because the `setup.py` file effectively is the manifest file used to discover which dependencies are needed, so when using it to detect dependencies we obviously don't have them yet. See https://packaging.python.org/guides/single-sourcing-package-version/
2021-03-19 13:32:16 +00:00
import codecs
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
import io
pyln: Change the setup.py file not to import the package This would lead to errors about missing dependencies when attempting to install using `pyhon setup.py install`. This is because the `setup.py` file effectively is the manifest file used to discover which dependencies are needed, so when using it to detect dependencies we obviously don't have them yet. See https://packaging.python.org/guides/single-sourcing-package-version/
2021-03-19 13:32:16 +00:00
import os.path
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
with io.open('README.md', encoding='utf-8') as f:
long_description = f.read()
pyln: Change the setup.py file not to import the package This would lead to errors about missing dependencies when attempting to install using `pyhon setup.py install`. This is because the `setup.py` file effectively is the manifest file used to discover which dependencies are needed, so when using it to detect dependencies we obviously don't have them yet. See https://packaging.python.org/guides/single-sourcing-package-version/
2021-03-19 13:32:16 +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
with io.open('requirements.txt', encoding='utf-8') as f:
requirements = [r for r in f.read().split('\n') if len(r)]
pyln: Change the setup.py file not to import the package This would lead to errors about missing dependencies when attempting to install using `pyhon setup.py install`. This is because the `setup.py` file effectively is the manifest file used to discover which dependencies are needed, so when using it to detect dependencies we obviously don't have them yet. See https://packaging.python.org/guides/single-sourcing-package-version/
2021-03-19 13:32:16 +00:00
def read(rel_path):
here = os.path.abspath(os.path.dirname(__file__))
with codecs.open(os.path.join(here, rel_path), 'r') as fp:
return fp.read()
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
setup(name='pyln-proto',
description='Pure python implementation of the Lightning Network protocol',
long_description=long_description,
long_description_content_type='text/markdown',
url='http://github.com/ElementsProject/lightning',
author='Christian Decker',
author_email='decker.christian@gmail.com',
license='MIT',
pyln.proto: fix package list in setup.py Remove non-existant pyln.proto.bolts. bolts will have separate setup.py, so we can rev the versions individually. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-06-16 22:20:30 +01:00
packages=['pyln.proto', 'pyln.proto.message'],
pyln.proto.message, pyln.proto.spec*: do magic to expose mypy types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-06-18 06:59:48 +01:00
package_data={'pyln.proto.message': ['py.typed']},
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
scripts=[],
zip_safe=True,
pyln: Derive version from git for pyln-proto
2021-09-23 13:48:07 +01:00
use_scm_version={
"root": "../..",
"relative_to": __file__,
"write_to": "contrib/pyln-proto/pyln/proto/__version__.py",
"write_to_template": "__version__ = \"{version}\"\n",
"version_scheme": "post-release",
"local_scheme": "no-local-version",
},
setup_requires=["setuptools_scm"],
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
install_requires=requirements)