zmk 0.1.0__tar.gz

zmk-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,86 @@
+name: Release
+
+on:
+  push:
+    tags: ["*"]
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ">=3.10"
+      - name: Install pypa/build
+        run: python3 -m pip install build --user
+      - name: Build wheel and source tarball
+        run: python3 -m build
+      - name: Store distribution packages
+        uses: actions/upload-artifact@v3
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish-to-pypi:
+    name: Publish Python distribution to PyPI
+    needs:
+      - build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/zmk
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v3
+        with:
+          name: python-package-distributions
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+  github-release:
+    name: GitHub release
+    needs:
+      - publish-to-pypi
+    runs-on: ubuntu-latest
+
+    permissions:
+      contents: write
+      id-token: write
+
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v3
+        with:
+          name: python-package-distributions
+          path: dist/
+      - name: Sign artifacts
+        uses: sigstore/gh-action-sigstore-python@v3.0.0
+        with:
+          inputs: >-
+            ./dist/*.tar.gz
+            ./dist/*.whl
+      - name: Create GitHub release
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        run: >-
+          gh release create
+          '${{ github.ref_name }}'
+          --repo '${{ github.repository }}'
+          --notes ""
+      - name: Upload artifact signatures to GitHub release
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        # Upload to GitHub Release using the `gh` CLI.
+        # `dist/` contains the built packages, and the
+        # sigstore-produced signatures and certificates.
+        run: >-
+          gh release upload
+          '${{ github.ref_name }}' dist/**
+          --repo '${{ github.repository }}'

zmk-0.1.0/.gitignore

@@ -0,0 +1,161 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+_version.py
+
+# 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/
+cover/
+
+# 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
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .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
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__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/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

zmk-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,22 @@
+fail_fast: false
+repos:
+  - repo: https://github.com/psf/black
+    rev: "23.9.1"
+    hooks:
+      - id: black
+  - repo: https://github.com/pycqa/isort
+    rev: "5.13.2"
+    hooks:
+      - id: isort
+  - repo: https://github.com/Lucas-C/pre-commit-hooks
+    rev: v1.5.2
+    hooks:
+      - id: remove-tabs
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.4.0
+    hooks:
+      - id: trailing-whitespace
+      - id: check-yaml
+        exclude: ^zmk/templates
+      - id: check-added-large-files
+      - id: check-shebang-scripts-are-executable

zmk-0.1.0/.vscode/settings.json

@@ -0,0 +1,25 @@
+{
+  "editor.formatOnSave": true,
+  "[python]": {
+    "editor.defaultFormatter": "ms-python.black-formatter",
+    "editor.codeActionsOnSave": {
+      "source.organizeImports": "always"
+    }
+  },
+  "[markdown][yaml]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[dts]": {
+    "editor.formatOnSave": false
+  },
+  "files.exclude": {
+    "**/__pycache__": true
+  },
+  "files.associations": {
+    "**/templates/board/**": "mako",
+    "**/templates/shield/**": "mako",
+    "**/templates/common/**": "mako"
+  },
+  "isort.check": true,
+  "isort.args": ["--profile", "black"]
+}

zmk-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 The ZMK Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

zmk-0.1.0/PKG-INFO

@@ -0,0 +1,290 @@
+Metadata-Version: 2.1
+Name: zmk
+Version: 0.1.0
+Summary: A command line program to help set up ZMK Firmware
+License: MIT License
+        
+        Copyright (c) 2023 The ZMK Contributors
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+Project-URL: Documentation, https://zmk.dev/docs
+Project-URL: Source Code, https://github.com/zmkfirmware/zmk-cli/
+Project-URL: Issue Tracker, https://github.com/zmkfirmware/zmk-cli/issues/
+Project-URL: Chat, https://zmk.dev/community/discord/invite
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: backports.strenum; python_version < "3.11"
+Requires-Dist: dacite<2.0.0,>=1.8.1
+Requires-Dist: mako<2.0.0,>=1.3.3
+Requires-Dist: rich<14.0.0,>=13.6.0
+Requires-Dist: ruamel.yaml<0.19.0,>=0.18.6
+Requires-Dist: shellingham<2.0.0,>=1.5.3
+Requires-Dist: typer<0.13.0,>=0.12.0
+Requires-Dist: west<2.0.0,>=1.2.0
+
+# ZMK CLI
+
+A command line program to help set up [ZMK Firmware](https://zmk.dev).
+
+ZMK CLI walks you through installing ZMK and setting up a GitHub repository to store and build custom firmware. It also automates some common tasks such as adding new keyboards to your repository.
+
+The instructions below contain commands that need to be run in a terminal program. On Windows, use the [Windows Terminal](https://apps.microsoft.com/detail/9n0dx20hk701) or PowerShell. On other operating systems, the terminal program is usually just named "Terminal".
+
+# Installation
+
+## Install Git
+
+Install Git from https://git-scm.com/downloads.
+
+If you have Windows 11, you can instead open a terminal and run:
+
+```
+winget install git.git
+```
+
+## Install Python
+
+ZMK CLI requires Python 3.10 or newer.
+
+### On Windows and macOS
+
+Install the latest version of Python from https://www.python.org/downloads/.
+
+If you have Windows 11, you can instead open a terminal and run:
+
+```sh
+winget install python3
+```
+
+### On Linux
+
+Most Linux distributions come with Python already installed. Open a terminal and run the following command to check its version:
+
+```sh
+python3 --version
+```
+
+If Python is not installed, install `python3` with your package manager.
+
+If the version is older than 3.10, you will need to find and install a package for a newer version of Python. On Ubuntu 20.04 and older, you can get Python 3.10 from the deadsnakes PPA with the following commands:
+
+```sh
+sudo add-apt-repository ppa:deadsnakes/ppa
+sudo apt install python3.10
+```
+
+You will then need to replace `python3` with `python3.10` in the rest of the installation instructions.
+
+## Install pipx
+
+ZMK CLI can be installed with pip, but using [pipx](https://github.com/pypa/pipx) is recommended to avoid conflicts between Python packages.
+
+### On Windows and Linux
+
+Open a terminal and run:
+
+```sh
+python3 -m pip install --user pipx
+python3 -m pipx ensurepath
+```
+
+Some Linux distributions may disallow installing packages with pip. If this gives you an error, see the [install instructions](https://github.com/pypa/pipx?tab=readme-ov-file#on-linux) specific to your distribution.
+
+Close and reopen your terminal, then run the following command. It should print a version number if everything is installed correctly:
+
+```sh
+pipx --version
+```
+
+### On macOS
+
+Open Terminal and run:
+
+```
+brew install pipx
+pipx ensurepath
+```
+
+## Install ZMK CLI
+
+Next, run the following commands:
+
+```sh
+pipx install zmk
+zmk --help
+```
+
+It should print a help message if everything installed correctly.
+
+On Linux, you may get an error saying you need to install another package such as `python3.10-venv`. If so, follow the instructions in the error message, then try the above commands again.
+
+# Usage
+
+All ZMK CLI commands start with `zmk`. Run `zmk --help` for general usage instructions. For help with a specific subcommand, add `--help` after the subcommand, e.g. `zmk init --help`.
+
+## Initialize a Repository
+
+> ⚠️ If you have already created a repo and cloned it to your computer, you do not need to run this command. Set the [user.home](#userhome) setting to point to the existing repo instead.
+
+The `zmk init` command walks you through creating a GitHub repository, then clones it to your computer so you can edit it.
+
+Open a terminal and use the `cd` command to move to a directory where you'd like to place the ZMK files, then run `zmk init`. For example:
+
+```sh
+cd ~/Documents
+zmk init
+```
+
+Follow the instructions it gives you. If you already have a ZMK config repo, you can enter its URL when prompted, for example:
+
+```
+Repository URL: https://github.com/myusername/zmk-config
+```
+
+Otherwise, leave this first prompt blank and press <kbd>Enter</kbd>, and it will walk you through creating a new repo.
+
+Once you finish following all the instructions, you will have a copy of the repo stored on your computer. All `zmk` commands will run on this repo (unless the working directory is inside a different repo). If you ever forget where the repo is located, you can run `zmk cd` to find it.
+
+Now that you have a repo created, see [Customizing ZMK](https://zmk.dev/docs/customization) for documentation on how to customize it, and see the instructions below for how ZMK CLI can automate some common tasks.
+
+## Keyboard Management
+
+### Add a Keyboard
+
+To start building firmware for a new keyboard, run `zmk keyboard add`. Follow the instructions to select a keyboard (and controller board if necessary), and it will add it to the list of firmware to build and copy a default keymap into your repo.
+
+You can then run `zmk code <keyboard>` to open the keymap in a text editor.
+
+This command reads from a local copy of ZMK to determine the supported keyboards. If the keyboard you want to use isn't listed, try running `zmk update` to update the local copy to the latest version of ZMK. If it still isn't listed, you may be able to find a [Zephyr module](#module-management) that provides it, you you may need to [create it yourself](#create-a-new-keyboard).
+
+### Remove a keyboard
+
+To remove a keyboard from the build, run `zmk keyboard remove` and select the item to remove. For a split keyboard, you will need to run this twice and remove the left and right sides.
+
+This simply removes a keyboard from the `build.yaml` file. It does not delete any `.keymap` or `.conf` files.
+
+### List Supported Keyboards
+
+Run `zmk keyboard list` to print a list of supported keyboard hardware.
+
+### Create a New Keyboard
+
+If ZMK doesn't support your keyboard yet, you can run `zmk keyboard new` to create a new keyboard from a template.
+
+This won't walk you through all of the details of adding support for a new keyboard, but it will generate most of the boilerplate for you. See the [New Keyboard Shield](https://zmk.dev/docs/development/new-shield) guide for how to finish writing the keyboard files.
+
+## Module Management
+
+[Zephyr modules](https://docs.zephyrproject.org/3.6.0/develop/modules.html) can add support for new keyboards, behaviors, and other features to ZMK. Use the `zmk module` command to install modules into your repo:
+
+```sh
+zmk module add     # Add a module
+zmk module remove  # Remove an installed module
+zmk module list    # List the installed modules
+zmk update         # Update the local copies of ZMK and modules to their latest versions
+```
+
+## Edit Keymap and Config Files
+
+The `zmk code` command will open ZMK files in a text editor:
+
+```sh
+zmk code                    # Open the repo directory in an editor
+zmk code <keyboard>         # Open <keyboard>.keymap in an editor
+zmk code --conf <keyboard>  # Open <keyboard>.conf in an editor
+zmk code --build            # Open build.yaml in an editor
+```
+
+The first time you run this command, it will ask you which editor you want to use. If you want to change this choice later or use an editor that wasn't listed, see the [core.editor](#coreeditor) and [code.explorer](#coreexplorer) settings.
+
+## Push Changes to GitHub
+
+Run `zmk cd` to go to the repo directory. From here, you can run `git` commands manage the repo.
+
+For example, after adding a keyboard to your repo and editing its keymap, you can run the following commands to push your changes to GitHub and trigger a firmware build:
+
+```sh
+git add .
+git commit
+git push
+```
+
+You will need to [authenticate with GitHub](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github#authenticating-with-the-command-line) before the `git push` command will work. The easiest way to do this is to install the [GitHub CLI](https://cli.github.com/) and run
+
+```sh
+gh auth login
+```
+
+but you can also use a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). If using an access token, make sure you create it with the "workflow" scope option selected.
+
+## Download Firmware from GitHub
+
+After pushing changes, GitHub will automatically build the firmware for you. Run `zmk download` (or `zmk dl` for short) to open the GitHub actions page in your browser.
+
+From this page, you can click on a build (the latest is at the top) to view its status. If the build succeeded, you can download the firmware from the "Artifacts" section at the bottom of the build summary page.
+
+## Configuration
+
+The `zmk config` command manages settings for ZMK CLI:
+
+```sh
+zmk config                 # List all settings
+zmk config <name>          # Print the value of the setting <name>
+zmk config <name> <value>  # Set <name> to <value>
+zmk config --unset <name>  # Remove the setting <name>
+```
+
+By default, these settings are stored in a file in your user profile directory. Run `zmk config --path` to get the location of this file. You can change where the settings file is stored by setting a `ZMK_CLI_CONFIG` environment variable to the new path to use, or by adding a `--config-file=<path>` argument when running `zmk`.
+
+Other commands use the following settings:
+
+### core.editor
+
+Command line for a text editor to use with the `zmk code` command.
+
+For example, so set Visual Studio Code as the editor and make it always open a new window, run:
+
+```sh
+zmk config core.editor "code --new-window"
+```
+
+### core.explorer
+
+Command line for a file explorer to use with the `zmk code` command when opening a directory.
+
+If this setting is not set, the `core.editor` tool will be run instead. Set this setting when using a text editor that does not support opening directories.
+
+### user.home
+
+The path to the repository to use whenever `zmk` is run and the working directory is not inside a ZMK config repository.
+
+For example, to point ZMK CLI to an existing repo at `~/Documents/zmk-config`, run:
+
+```sh
+zmk config user.home ~/Documents/zmk-config
+```