theengsgateway 1.6.0__tar.gz

theengsgateway-1.6.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Data processed
+2. Expected data
+3. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment**
+Output of `python -m TheengsGateway.diagnose` or `python -m TheengsGateway.diagnose -c path_to_conf_file` if not using the default path for the configuration file.
+
+**Additional context**
+Add any other relevant context about the problem here.

theengsgateway-1.6.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

theengsgateway-1.6.0/.github/pull_request_template.md

@@ -0,0 +1,6 @@
+## Description:
+
+## Checklist:
+  - [ ] I have created the pull request against the latest development branch
+  - [ ] I have added only one feature/fix per PR and the code change compiles without warnings
+  - [ ] I accept the [Developer Certificate of Origin (DCO)](https://github.com/theengs/gateway/blob/development/docs/participate/development.md#developer-certificate-of-origin).

theengsgateway-1.6.0/.github/workflows/manual_test-pypi.yml

@@ -0,0 +1,25 @@
+name: Publish distribution to TestPyPI
+on:
+  workflow_dispatch:
+jobs:
+  build-n-publish:
+    name: Build and publish distribution to TestPyPI
+    runs-on: ubuntu-22.04
+    steps:
+    - uses: actions/checkout@v3
+      with: {fetch-depth: 0}  # deep clone for setuptools-scm
+    - uses: actions/setup-python@v4
+      with:
+        python-version: '3.12'
+    - name: Install pypa/build
+      run: |
+        python3 -m pip install --upgrade pip
+        pip3 install setuptools setuptools_scm cmake wheel scikit-build ninja
+    - name: Build a source tarball
+      run: |
+        python3 setup.py sdist
+    - name: Publish distribution 📦 to Test PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        password: ${{ secrets.TEST_PYPI_API_TOKEN }}
+        repository-url: https://test.pypi.org/legacy/

theengsgateway-1.6.0/.github/workflows/publish_docs.yml

@@ -0,0 +1,36 @@
+name: Create and publish documentation
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+jobs:
+  documentation:
+    runs-on: ubuntu-22.04
+    name: Create the documentation and deploy it to GitHub Pages
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "14.x"
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: "3.12"
+      - name: Install build dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install requests
+          npm install
+      - name: Download Common Config
+        run: |
+          curl -o docs/.vuepress/public/commonConfig.js https://www.theengs.io/commonConfig.js
+      - name: Build documentation
+        run: |
+          npm run docs:build
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: ./docs/.vuepress/dist
+          cname: gateway.theengs.io

theengsgateway-1.6.0/.github/workflows/release.yml

@@ -0,0 +1,26 @@
+name: Publish distributions to PyPI and documentation to GH pages
+on:
+  release:
+    types: [published]
+
+jobs:
+  build-n-publish:
+    name: Build and publish distributions to PyPI
+    runs-on: ubuntu-22.04
+    steps:
+    - uses: actions/checkout@v3
+      with: {fetch-depth: 0}  # deep clone for setuptools-scm
+    - uses: actions/setup-python@v4
+      with:
+        python-version: '3.12'
+    - name: Install pypa/build
+      run: |
+        python3 -m pip install --upgrade pip
+        pip3 install setuptools setuptools_scm cmake wheel scikit-build ninja
+    - name: Build a source tarball
+      run: |
+        python3 setup.py sdist
+    - name: Publish distribution 📦 to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        password: ${{ secrets.PYPI_API_TOKEN }}

theengsgateway-1.6.0/.github/workflows/test.yml

@@ -0,0 +1,50 @@
+name: Test build
+
+on:
+  pull_request:
+
+jobs:
+  docs:
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+      - name: Vale
+        uses: pre-commit/action@v3.0.0
+        with:
+          extra_args: --all-files vale
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        python:
+          - "3.8"   # oldest Python supported by PSF
+          - "3.9"
+          - "3.10"
+          - "3.11"
+          - "3.12"  # newest stable Python
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with: {fetch-depth: 0}  # deep clone for setuptools-scm
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python }}
+      - name: Mypy
+        uses: pre-commit/action@v3.0.0
+        with:
+          extra_args: --all-files mypy
+      - name: Install requirements
+        run: |
+          pip3 install --upgrade pip
+          pip3 install setuptools setuptools_scm cmake wheel scikit-build ninja
+      - name: Build package
+        run: |
+          python3 setup.py sdist
+      - uses: actions/upload-artifact@v4
+        if: ${{ matrix.python == 3.12 }}
+        with:
+          name: python-package
+          path: dist/

theengsgateway-1.6.0/.gitignore

@@ -0,0 +1,136 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+_skbuild
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# VuePress
+node_modules/
+
+# Vale styles
+vale/styles/Google

theengsgateway-1.6.0/.npmignore

@@ -0,0 +1,12 @@
+pids
+logs
+node_modules
+npm-debug.log
+coverage/
+run
+dist
+.DS_Store
+.nyc_output
+.basement
+config.local.js
+basement_dist

theengsgateway-1.6.0/.pre-commit-config.yaml

@@ -0,0 +1,24 @@
+---
+repos:
+- repo: https://github.com/errata-ai/vale
+  rev: 'v3.0.4'
+  hooks:
+    - id: vale
+      name: vale-sync
+      pass_filenames: false
+      args: [sync]
+    - id: vale
+- repo: https://github.com/pre-commit/mirrors-mypy
+  rev: v1.8.0
+  hooks:
+  - id: mypy
+    entry: env MYPYPATH=TheengsGateway mypy
+    args: []
+    additional_dependencies:
+    - bleak>=0.19.0
+    - bluetooth-adapters>=0.15.3; python_version>="3.9"
+    - bluetooth-clocks<1.0
+    - bluetooth-numbers>=1.0,<2.0
+    - importlib-metadata
+    - paho-mqtt>=2.0.0,<3.0.0
+    - theengsdecoder>=1.9.5

theengsgateway-1.6.0/.vale.ini

@@ -0,0 +1,13 @@
+StylesPath = "vale/styles"
+MinAlertLevel = suggestion
+Vocab = Theengs
+Packages = Google
+
+[*.md]
+BasedOnStyles = Vale, Google
+Google.Ellipses = NO
+Google.FirstPerson = NO
+Google.Headings = NO
+Google.Parens = NO
+Google.WordList = NO
+Google.We = NO

theengsgateway-1.6.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+<!-- vale Google.Passive = NO -->
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what's best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that aren't aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at untechnophile@gmail.com. The project team reviews and investigates all complaints, and responds in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who don't follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant homepage](https://contributor-covenant.org), [version 1.4](https://contributor-covenant.org/version/1/4/).