pax_global_header 0000666 0000000 0000000 00000000064 15175762040 0014521 g ustar 00root root 0000000 0000000 52 comment=921b1fa36afa2faca35f5e54d366f27816bed407 BrianPugh-cyclopts-921b1fa/ 0000775 0000000 0000000 00000000000 15175762040 0015645 5 ustar 00root root 0000000 0000000 BrianPugh-cyclopts-921b1fa/.codecov.yml 0000664 0000000 0000000 00000000601 15175762040 0020065 0 ustar 00root root 0000000 0000000 coverage: status: project: default: # Commits pushed to main should not make the overall # project coverage decrease by more than 2% target: auto threshold: 2% patch: default: # Be tolerant on code coverage diff on PRs to limit # noisy red coverage status on github PRs. target: auto threshold: 20% BrianPugh-cyclopts-921b1fa/.github/ 0000775 0000000 0000000 00000000000 15175762040 0017205 5 ustar 00root root 0000000 0000000 BrianPugh-cyclopts-921b1fa/.github/FUNDING.yml 0000664 0000000 0000000 00000001456 15175762040 0021030 0 ustar 00root root 0000000 0000000 # These are supported funding model platforms github: [BrianPugh]# Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] patreon: # Replace with a single Patreon username open_collective: # Replace with a single Open Collective username ko_fi: # Replace with a single Ko-fi username tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry liberapay: # Replace with a single Liberapay username issuehunt: # Replace with a single IssueHunt username otechie: # Replace with a single Otechie username lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] BrianPugh-cyclopts-921b1fa/.github/contributing.md 0000664 0000000 0000000 00000005525 15175762040 0022245 0 ustar 00root root 0000000 0000000 ## Environment Setup 1. We use [uv](https://docs.astral.sh/uv/) for managing virtual environments and dependencies. Once uv is installed, run `uv sync --all-extras` in this repo to get started. 2. For managing linters, static-analysis, and other tools, we use [pre-commit](https://pre-commit.com/#installation). Once Pre-commit is installed, run `uv run pre-commit install` in this repo to install the hooks. Using pre-commit ensures PRs match the linting requirements of the codebase. ## Documentation Whenever possible, please add docstrings to your code! We use [numpy-style napoleon docstrings](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/#google-vs-numpy). To confirm docstrings are valid, build the docs by running `uv run make html` in the `docs/` folder. I typically write docstrings first, it will act as a guide to limit scope and encourage unit-testable code. Good docstrings include information like: 1. If not immediately obvious, what is the intended use-case? When should this function be used? 2. What happens during errors/edge-cases. 3. When dealing with physical values, include units. ## Unit Tests We use the [pytest](https://docs.pytest.org/) framework for unit testing. Ideally, all new code is partnered with new unit tests to exercise that code. If fixing a bug, consider writing the test first to confirm the existence of the bug, and to confirm that the new code fixes it. Unit tests should only test a single concise body of code. If this is hard to do, there are two solutions that can help: 1. Restructure the code. Keep inputs/outputs to be simple variables. Avoid complicated interactions with state. 2. Use [pytest-mock](https://pytest-mock.readthedocs.io/en/latest/) to mock out external interactions. 3. Run tests with `python -m pytest`. ## Coding Style In an attempt to keep consistency and maintainability in the code-base, here are some high-level guidelines for code that might not be enforced by linters. * Use f-strings. * Keep/cast path variables as `pathlib.Path` objects. Do not use `os.path`. For public-facing functions, cast path arguments immediately to `Path`. * Use magic-methods when appropriate. It might be better to implement ``MyClass.__call__()`` instead of ``MyClass.run()``. * Do not return sentinel values for error-states like `-1` or `None`. Instead, raise an exception. * Avoid deeply nested code. Techniques like returning early and breaking up a complicated function into multiple functions results in easier to read and test code. * Consider if you are double-name-spacing and how modules are meant to be imported. E.g. it might be better to name a function `read` instead of `image_read` in the module `my_package/image.py`. Consider the module name-space and whether or not it's flattened in `__init__.py`. * Only use multiple-inheritance if using a mixin. Mixin classes should end in `"Mixin"`. BrianPugh-cyclopts-921b1fa/.github/dependabot.yml 0000664 0000000 0000000 00000000766 15175762040 0022046 0 ustar 00root root 0000000 0000000 # To get started with Dependabot version updates, you'll need to specify which # package ecosystems to update and where the package manifests are located. # Please see the documentation for all configuration options: # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates version: 2 updates: - package-ecosystem: "pip" # See documentation for possible values directory: "/" # Location of package manifests schedule: interval: "weekly" BrianPugh-cyclopts-921b1fa/.github/workflows/ 0000775 0000000 0000000 00000000000 15175762040 0021242 5 ustar 00root root 0000000 0000000 BrianPugh-cyclopts-921b1fa/.github/workflows/deploy.yaml 0000664 0000000 0000000 00000001662 15175762040 0023427 0 ustar 00root root 0000000 0000000 name: Build package and push to PyPi on: workflow_dispatch: push: tags: - "v*.*.*" jobs: build: runs-on: ubuntu-latest env: PYTHON: 3.12 steps: - name: Check out repository uses: actions/checkout@v4 with: fetch-depth: 0 # Needed for hatch-vcs to get version from git tags - name: Install uv uses: astral-sh/setup-uv@v5 with: enable-cache: true - name: Set up python ${{ env.PYTHON }} id: setup-python run: uv python install ${{ env.PYTHON }} - name: Install project run: uv sync --all-extras - name: Build package run: uv build - name: Publish package if: github.event_name != 'workflow_dispatch' run: uv publish --token ${{ secrets.PYPI_TOKEN }} - uses: actions/upload-artifact@v4 if: always() with: name: dist path: dist/ BrianPugh-cyclopts-921b1fa/.github/workflows/tests.yaml 0000664 0000000 0000000 00000005560 15175762040 0023276 0 ustar 00root root 0000000 0000000 # Regular tests # # Use this to ensure your tests are passing on every push and PR (skipped on # pushes which only affect documentation). # # You should make sure you run jobs on at least the *oldest* and the *newest* # versions of python that your codebase is intended to support. name: tests on: push: branches: - main pull_request: jobs: test: timeout-minutes: 45 defaults: run: shell: bash runs-on: ${{ matrix.os }} strategy: fail-fast: false matrix: os: [ubuntu-latest, macos-15, windows-latest] python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] env: OS: ${{ matrix.os }} PYTHON: ${{ matrix.python-version }} steps: - name: Set OS Environment Variables (Windows) if: runner.os == 'Windows' run: | echo 'ACTIVATE_PYTHON_VENV=.venv/scripts/activate' >> $GITHUB_ENV - name: Set OS Environment Variables (not Windows) if: runner.os != 'Windows' run: | echo 'ACTIVATE_PYTHON_VENV=.venv/bin/activate' >> $GITHUB_ENV - name: Check out repository uses: actions/checkout@v4 with: fetch-depth: 0 # Needed for hatch-vcs to get version from git tags - name: Install uv uses: astral-sh/setup-uv@v5 with: enable-cache: true - name: Set up python ${{ matrix.python-version }} id: setup-python run: uv python install ${{ matrix.python-version }} - name: Install library run: uv sync --all-extras - name: Cache pre-commit uses: actions/cache@v4 with: path: ~/.cache/pre-commit/ key: pre-commit-${{ runner.os }}-${{ env.pythonLocation }}-${{ hashFiles('.pre-commit-config.yaml') }} - name: Pre-commit run run: uv run pre-commit run --show-diff-on-failure --color=always --all-files - name: Check tests folder existence id: check_test_files uses: andstor/file-existence-action@v3 with: files: "tests" - name: Run tests if: steps.check_test_files.outputs.files_exists == 'true' run: | uv run pytest --run-slow --cov=cyclopts --cov-config=pyproject.toml --cov-report term --cov-report xml --junitxml=testresults.xml uv run coverage report - name: Upload coverage to Codecov if: steps.check_test_files.outputs.files_exists == 'true' uses: codecov/codecov-action@v4 with: token: ${{ secrets.CODECOV_TOKEN }} flags: unittests env_vars: OS,PYTHON name: Python ${{ matrix.python-version }} on ${{ runner.os }} #---------------------------------------------- # make sure docs build #---------------------------------------------- - name: Build HTML docs run: uv run sphinx-build -b html -W docs/source/ docs/build/html BrianPugh-cyclopts-921b1fa/.gitignore 0000664 0000000 0000000 00000010252 15175762040 0017635 0 ustar 00root root 0000000 0000000 ##--------------------------------------------------- # Automated documentation .gitignore files ##--------------------------------------------------- # Automatically generated API documentation stubs from sphinx-apidoc docs/source/packages # Automatically converting README from markdown to rST docs/bin docs/source/readme.rst docs/source/assets ##--------------------------------------------------- # Continuous Integration .gitignore files ##--------------------------------------------------- # Ignore test result XML files testresults.xml coverage.xml ##--------------------------------------------------- # Python default .gitignore ##--------------------------------------------------- # Byte-compiled / optimized / DLL files __pycache__/ *.py[cod] *$py.class # C extensions *.so *.pyd # 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 .hypothesis/ .pytest_cache/ # Translations *.mo *.pot # Django stuff: *.log local_settings.py db.sqlite3 # Flask stuff: instance/ .webassets-cache # Scrapy stuff: .scrapy # Sphinx documentation /docs/_build/ /docs/build/ # PyBuilder target/ # Pycharm /.idea/dictionaries /.idea/modules.xml /.idea/shelf /.idea/usage.statistics.xml /.idea/workspace.xml # 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 # celery beat schedule file celerybeat-schedule # 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/ ##--------------------------------------------------- # Windows default .gitignore ##--------------------------------------------------- # Windows thumbnail cache files Thumbs.db ehthumbs.db ehthumbs_vista.db # Dump file *.stackdump # Folder config file [Dd]esktop.ini # Recycle Bin used on file shares $RECYCLE.BIN/ # Windows Installer files *.cab *.msi *.msix *.msm *.msp # Windows shortcuts *.lnk ##--------------------------------------------------- # Linux default .gitignore ##--------------------------------------------------- # Editor backup files *~ # temporary files which can be created if a process still has a handle open of a deleted file .fuse_hidden* # KDE directory preferences .directory # Linux trash folder which might appear on any partition or disk .Trash-* # .nfs files are created when an open file is removed but is still being accessed .nfs* ##--------------------------------------------------- # Mac OSX default .gitignore ##--------------------------------------------------- # General .DS_Store .AppleDouble .LSOverride # Icon must end with two \r Icon # Thumbnails ._* # Files that might appear in the root of a volume .DocumentRevisions-V100 .fseventsd .Spotlight-V100 .TemporaryItems .Trashes .VolumeIcon.icns .com.apple.timemachine.donotpresent # Directories potentially created on remote AFP share .AppleDB .AppleDesktop Network Trash Folder Temporary Items .apdisk # Cython cyclopts/_c_extension.c cyclopts/*.html # Auto-generated version file (only exists after build) cyclopts/_version.py # line-profiler *.lprof # Misc dev /*.py /draw.toml /*.md /*.html /*.rst # Editor config .vscode poetry.lock tests/**/uv.lock /coverage.json BrianPugh-cyclopts-921b1fa/.pre-commit-config.yaml 0000664 0000000 0000000 00000002701 15175762040 0022126 0 ustar 00root root 0000000 0000000 exclude: ^(uv.lock|.idea/|tests/__snapshots__/) repos: - repo: https://github.com/astral-sh/ruff-pre-commit rev: "v0.14.2" hooks: - id: ruff args: [--fix, --exit-non-zero-on-fix] - id: ruff-format - repo: https://github.com/pre-commit/pre-commit-hooks rev: v6.0.0 hooks: - id: check-added-large-files - id: check-case-conflict - id: check-shebang-scripts-are-executable - id: check-merge-conflict - id: check-json - id: check-toml - id: check-xml - id: check-yaml - id: debug-statements exclude: '^tests/(test_py3.*\.py|py312/)' - id: destroyed-symlinks - id: detect-private-key - id: end-of-file-fixer exclude: ^LICENSE|\.(html|csv|txt|svg|py)$ - id: pretty-format-json args: ["--autofix", "--no-ensure-ascii", "--no-sort-keys"] - id: requirements-txt-fixer - id: trailing-whitespace args: [--markdown-linebreak-ext=md] exclude: \.(html|svg)$ - repo: https://github.com/fredrikaverpil/creosote.git rev: v4.1.0 hooks: - id: creosote - repo: https://github.com/codespell-project/codespell rev: v2.4.1 hooks: - id: codespell additional_dependencies: - tomli - repo: https://github.com/crate-ci/typos rev: v1 hooks: - id: typos - repo: https://github.com/RobertCraigie/pyright-python rev: v1.1.408 hooks: - id: pyright BrianPugh-cyclopts-921b1fa/.readthedocs.yaml 0000664 0000000 0000000 00000001261 15175762040 0021074 0 ustar 00root root 0000000 0000000 # Read the Docs configuration file # See https://docs.readthedocs.io/en/stable/config-file/v2.html for details # Required version: 2 build: os: "ubuntu-22.04" tools: python: "3.10" jobs: post_create_environment: # Install uv - pip install uv post_install: # Install project with 'docs' extra using uv pip - uv pip install -e .[docs] # Build documentation in the docs/ directory with Sphinx sphinx: configuration: docs/source/conf.py fail_on_warning: true # Prevent ReadTheDocs from installing the package automatically python: install: [] # If using Sphinx, optionally build your docs in additional formats such as PDF formats: - pdf BrianPugh-cyclopts-921b1fa/CONTRIBUTING.md 0000664 0000000 0000000 00000010053 15175762040 0020075 0 ustar 00root root 0000000 0000000 # Contributing to Cyclopts Thank you for your interest in contributing to Cyclopts! This guide will help you get started. ## Code of Conduct Please be respectful and constructive in all interactions. We are committed to providing a welcoming and inclusive experience for everyone. ## Where to Start Looking for something to work on? Check out issues labeled [`good first issue`](https://github.com/BrianPugh/cyclopts/labels/good%20first%20issue) on GitHub. These are curated to be approachable for new contributors. If you're exploring the codebase, these are good entry points: - `cyclopts/core.py` — the main `App` class and CLI lifecycle - `cyclopts/bind.py` — token-to-parameter binding - `cyclopts/_convert.py` — type conversion logic - `cyclopts/parameter.py` — parameter configuration API ## Getting Started ### Prerequisites - Python 3.10 or later - [uv](https://docs.astral.sh/uv/) (recommended package manager) ### Setting Up Your Development Environment 1. Fork and clone the repository: ```bash # Replace with your fork URL, if appropriate git clone https://github.com/BrianPugh/cyclopts.git cd cyclopts ``` 2. Install dependencies (including dev extras): ```bash uv sync --all-extras ``` 3. Install pre-commit hooks: ```bash uv run pre-commit install ``` ## Development Workflow ### Running Tests ```bash # Run all tests uv run pytest # Run all tests with coverage uv run pytest --cov=cyclopts --cov-config=pyproject.toml --cov-report term # Run a specific test file uv run pytest tests/test_core.py # Run a specific test function uv run pytest tests/test_core.py::test_function_name ``` Tests automatically run in isolated temporary directories. Python 3.12+ specific tests live in `tests/py312/` and are skipped on older versions. ### Linting and Formatting Pre-commit hooks run automatically on `git commit`. You can also run them manually: ```bash # Run all checks uv run pre-commit run --all-files # Run individual tools uv run ruff check --fix # Linting uv run ruff format # Formatting uv run pyright # Type checking ``` ### Code Style - **Line length:** 120 characters - **Docstrings:** NumPy-style convention - **Type hints:** Pyright strict mode - **Target Python:** 3.10+ (do not use syntax or features exclusive to newer versions without version guards) ### Building Documentation ```bash cd docs make html ``` ## Submitting Changes ### Pull Requests 1. Create a feature branch from `main`. 2. Make your changes, adding tests for new functionality. 3. Ensure all checks pass: ```bash uv run pre-commit run --all-files uv run pytest ``` 4. Push your branch and open a pull request against `main`. ### Commit Messages and PR Descriptions - Write clear, concise commit messages describing *what* changed and *why*. - Reference related issues in your PR description (e.g., `Fixes #123`). - There is no changelog to update — that is handled by the maintainers. ## Testing a Pull Request If a PR has been opened to fix an issue you reported, you can test it by installing Cyclopts directly from the PR branch: ```bash pip install git+https://github.com/BrianPugh/cyclopts.git@branch-name ``` Or with uv: ```bash uv pip install git+https://github.com/BrianPugh/cyclopts.git@branch-name ``` Replace `branch-name` with the branch listed on the PR. Alternatively, you can clone the repo and install in editable mode into your project's virtual environment: ```bash git clone https://github.com/BrianPugh/cyclopts.git cd cyclopts git checkout branch-name # Activate your project's virtual environment, then: pip install -e . ``` Verify the fix against your original reproducer and report back on the PR. ## Reporting Issues Open an issue on [GitHub](https://github.com/BrianPugh/cyclopts/issues) with: - A minimal reproducible example. - Your Python version and Cyclopts version (`python -c "import cyclopts; print(cyclopts.__version__)"`). - The expected vs. actual behavior. ## License By contributing, you agree that your contributions will be licensed under the [Apache License 2.0](LICENSE). BrianPugh-cyclopts-921b1fa/LICENSE 0000664 0000000 0000000 00000026135 15175762040 0016661 0 ustar 00root root 0000000 0000000 Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright CURRENT_YEAR_HERE YOUR_NAME_HERE Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. BrianPugh-cyclopts-921b1fa/README.md 0000664 0000000 0000000 00000023545 15175762040 0017135 0 ustar 00root root 0000000 0000000