endurancepy 0.1.0__tar.gz

endurancepy-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report something that isn't working as expected
+title: "[Bug] "
+labels: bug
+assignees: ''
+---
+
+## Description
+
+A clear and concise description of the bug.
+
+## To reproduce
+
+Steps (or a minimal code snippet) to reproduce the behaviour:
+
+```python
+import endurancepy as ep
+# ...
+```
+
+## Expected behaviour
+
+What you expected to happen.
+
+## Actual behaviour
+
+What actually happened (include the full error traceback if any).
+
+## Context
+
+- Series / season / event / session involved (e.g. WEC 2024 Le Mans, Race):
+- EndurancePy version / commit:
+- Python version:
+- OS:
+
+## Additional notes
+
+Anything else that might help — but **do not attach raw Al Kamel timing files**
+(they are not redistributable). A small synthetic example is fine.

endurancepy-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Question / discussion
+    url: https://github.com/RomainFl50/EndurancePy/discussions
+    about: Ask a question or discuss ideas before opening an issue.

endurancepy-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: Suggest a feature, an API, or a series/season to support
+title: "[Feature] "
+labels: enhancement
+assignees: ''
+---
+
+## Problem / motivation
+
+What are you trying to do, and what's missing today?
+
+## Proposed solution
+
+Describe the feature or API you'd like. If it mirrors something in FastF1, please
+link or name the equivalent.
+
+```python
+# Sketch of the desired API, if relevant
+```
+
+## Series / scope
+
+Which series or seasons does this concern (WEC, ELMS, AsLMS, Le Mans Cup, IMSA)?
+
+## Alternatives considered
+
+Any alternative approaches you've thought about.
+
+## Additional context
+
+Anything else (links to public result pages, references, etc.).

endurancepy-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,29 @@
+## Summary
+
+Briefly describe what this PR does and why.
+
+## Related issue
+
+Closes #<!-- issue number, if any -->
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation
+- [ ] Refactor / chore
+- [ ] Tests
+
+## Checklist
+
+- [ ] I have read the [CONTRIBUTING](../CONTRIBUTING.md) guide.
+- [ ] My change follows the design in `docs/` (analysis & implementation plan).
+- [ ] `ruff` (format + check) and `mypy` pass.
+- [ ] Tests pass (`pytest`) and I added tests for new logic.
+- [ ] I did **not** commit any raw Al Kamel timing data; fixtures are synthetic
+      or otherwise redistributable.
+- [ ] Documentation / docstrings updated where relevant.
+
+## Notes for reviewers
+
+Anything specific you'd like reviewers to focus on.

endurancepy-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,47 @@
+name: CI
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+    branches: ["main"]
+  workflow_dispatch:
+
+jobs:
+  lint:
+    name: Lint & type-check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install dev dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Ruff (format check)
+        run: ruff format --check .
+      - name: Ruff (lint)
+        run: ruff check .
+      - name: Mypy
+        run: mypy src
+
+  test:
+    name: Tests (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install package with dev extras
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Run tests
+        run: pytest -m "not network" --cov=endurancepy --cov-report=term-missing

endurancepy-0.1.0/.github/workflows/integration.yml

@@ -0,0 +1,23 @@
+name: integration
+
+# On-demand end-to-end test against the live Al Kamel portal. Runs only when
+# manually dispatched (GitHub Actions runners have open internet access, unlike
+# the default development environment).
+
+on:
+  workflow_dispatch:
+
+jobs:
+  integration:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install package with dev extras
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Run network integration tests
+        run: pytest -m network -q

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

@@ -0,0 +1,47 @@
+name: release
+
+# Build the package and publish it to PyPI when a version tag is pushed.
+# Publishing uses PyPI Trusted Publishing (OIDC) — no API token/secret is stored
+# in the repo. See RELEASING.md for the one-time PyPI setup.
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade pip build
+          python -m build
+      - name: Check metadata
+        run: |
+          python -m pip install --upgrade "twine>=6" "packaging>=24.2"
+          python -m twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    if: startsWith(github.ref, 'refs/tags/v')
+    environment: pypi
+    permissions:
+      id-token: write  # required for Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

endurancepy-0.1.0/.gitignore

@@ -0,0 +1,75 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# 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
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# IDEs
+.idea/
+.vscode/
+*.swp
+
+# OS
+.DS_Store
+Thumbs.db
+
+# EndurancePy data cache (downloaded Al Kamel / timing archives)
+cache/
+*.cache
+.endurancepy_cache/
+
+# Documentation builds
+docs/_build/
+site/
+
+# mypy / type checkers
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.pyre/
+.ruff_cache/

endurancepy-0.1.0/CHANGELOG.md

@@ -0,0 +1,143 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-06-16
+
+First release: load endurance racing timing & results data (WEC, ELMS, AsLMS,
+Le Mans Cup, IMSA) from the Al Kamel archives, with a FastF1-style API.
+
+### Fixed
+
+- Discovery: decode (`unquote`) the portal's percent-encoded result paths so
+  built URLs are encoded exactly once (no more `%2520`), and make event/session
+  matching prefer substring containment then `partial_ratio` (short queries like
+  `"Spa"` no longer mis-resolve). Verified end-to-end against the live portal.
+
+### Added
+
+- Championship standings (milestone 3.1): `compute_standings(results, ...)`
+  aggregates points across rounds into a `Standings` table — configurable points
+  system (named / sequence / mapping), `by` car/crew/team/manufacturer, overall
+  or `per_class`. A generic calculator, not a replica of any series' exact rules.
+  Exposed as `ep.compute_standings` / `ep.Standings`.
+- Event schedule (milestone 3.0): `get_event_schedule(year, series, season=...)`
+  builds an `EventSchedule` (one row per event: round, name, date, sessions)
+  from a season's discovered files; `get_event(...)`, `EventSchedule`
+  `get_event_by_round`/`get_event_by_name`, and `Event.get_session`/`get_race`
+  (the returned session carries its season so `load()` needs no `season=`).
+  `discovery.build_events` / `session_datetime` underpin it.
+- Examples (`examples/`): `quickstart.py` and `quickstart.ipynb` (load a real
+  session via `season=`), `lap_analysis.py` (offline analysis of a local
+  Analysis CSV) and `plot_pace_by_class.py` (green-flag pace box plot). The
+  offline examples are executed in the test suite so they don't rot.
+- Top-level convenience re-exports: `read_analysis`, `read_classification`,
+  `read_weather`.
+- Project groundwork: MIT `LICENSE`, `README`, `.gitignore`.
+- Design documentation:
+  - `docs/analyse_fastf1.md` — exhaustive inventory of FastF1's content and its
+    mapping onto endurance / Al Kamel data.
+  - `docs/plan_implementation.md` — phase-2 implementation plan.
+- Community health files: `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, GitHub issue
+  templates and a pull request template.
+- Continuous integration workflow (ruff, mypy, pytest).
+- Package skeleton under `src/endurancepy/` (milestone 2.0): the public API
+  surface (`get_session`, `get_event`, `get_event_schedule`, `Cache`, `Series`,
+  `set_log_level`), data-object class stubs (`Session`, `Laps`/`Lap`,
+  `SessionResults`/`CarResult`, `Event`/`EventSchedule`), the `Series` registry,
+  reference column schemas, exceptions, logging, and the Al Kamel parser module
+  layout (data loading not implemented yet). Project tooling (`pyproject.toml`
+  with Hatchling, ruff, mypy, pytest) and a smoke-test suite.
+- Cache and Al Kamel client (milestone 2.1):
+  - `Cache`: two-stage on-disk cache — stage 1 raw HTTP via `requests-cache`
+    (SQLite), stage 2 parsed `DataFrame`s as Parquet plus JSON metadata,
+    namespaced by `PARSER_VERSION`. Includes `enable_cache`, `clear_cache`,
+    `get_cache_info`, `set_disabled`/`set_enabled`, `disabled()` context
+    manager, `offline_mode`, and dataframe/metadata save/load helpers.
+  - `alkamel.client`: `build_results_url` (verified `Results/...` tree, URL
+    encoding, optional `Hour N`) and a cache-aware `download`.
+  - Offline tests covering URL building, Parquet round-trips and the
+    download path.
+- Analysis CSV parser (milestone 2.2 — the core):
+  - `alkamel.timeparse`: tolerant duration parsing (`SS.mmm` / `M:SS.mmm` /
+    `H:MM:SS.mmm`, including the >24h rollover).
+  - `alkamel.headers.read_alkamel_csv`: tolerant CSV reading (BOM, leading-space
+    headers, trailing separator, all values as stripped strings).
+  - `alkamel.analysis.to_laps`/`read_analysis`: map the Analysis CSV to `Laps`
+    and derive `Stint`, `PitInTime`/`PitOutTime`, `LapStartTime`, the cumulative
+    `SectorNSessionTime`, overall and in-class `Position`, `IsPersonalBest`,
+    `IsAccurate` and `DriverChange`. (Gaps, `Hour` and `LapStartDate` need
+    session context and are filled later.)
+  - `Laps.pick_*` filters implemented: `pick_cars`, `pick_classes`,
+    `pick_manufacturers`, `pick_stints`, `pick_drivers`, `pick_teams`,
+    `pick_laps`, `pick_fastest`, `pick_quicklaps`, `pick_track_status`,
+    `pick_wo_box`, `pick_box_laps`, `pick_accurate`; plus
+    `SessionResults.pick_classes`.
+  - Synthetic Analysis-CSV fixture and tests (multi-class, multi-driver, a pit
+    stop and an FCY lap).
+- Session results from laps (milestone 2.3):
+  - `results.from_laps`: reconstructs `SessionResults` (one row per car/crew)
+    from the laps — final order by laps then total time, overall and per class,
+    with each car's `Crew`, `BestLapTime`, lap count and total time. (The
+    Classification-CSV parser is deferred until its format is verified.)
+  - `Session.results` now derives from `laps` when available; `Session.cars`
+    (finishing order) and `Session.get_car` implemented.
+  - Added `Crew` and `BestLapTime` to the results schema; tests for the
+    derivation and the session car helpers.
+- Track-status timeline (milestone 2.4):
+  - `track_status.from_laps`: reconstructs the session flag timeline (one row
+    per change) from the laps' finish-line flags, with a flag registry mapping
+    raw codes (GF/FCY/SC/SF/FF/Code60/…) to readable statuses.
+  - `Session.track_status` now derives from `laps` when available.
+  - (The Weather-CSV parser is deferred until its format is verified.)
+- Session loading (milestone 2.5):
+  - `Session.load(source=...)` reads an Analysis CSV from a path, bytes or
+    `http(s)` URL into `Session.laps` (results and track status derive from it);
+    parsed laps are cached as Parquet and reused on a subsequent `load()`.
+  - Raises `SessionNotAvailableError` when no source is given and the laps are
+    not cached. (Automatic discovery of remote files and the `Event`/
+    `EventSchedule` layer remain to be implemented.)
+- Automatic discovery in `Session.load` (milestone 2.9):
+  - `Session.load(season="<NN_YYYY>")` downloads the portal `?season=` index,
+    fuzzy-matches the event and session names, and downloads the Analysis,
+    Classification and Weather CSVs automatically (latest hour for races).
+  - `discovery.resolve_session_files` / `fetch_index`; `Series.keyword` to
+    select the right series folder.
+  - Offline tests for the resolution logic; a `network`-marked end-to-end
+    integration test (self-skips when the portal is unreachable) plus a manual
+    `integration` GitHub Actions workflow to run it on a networked runner.
+- Race Classification parser (milestone 2.8):
+  - `alkamel.classification.read_classification`/`to_results`: parse the race
+    Classification CSV (`POSITION;NUMBER;TEAM;DRIVER_1..5;VEHICLE;CLASS;STATUS;
+    LAPS;TOTAL_TIME;FL_TIME;...`) into `SessionResults`, handling the
+    apostrophe time format (`5:44'41.101`) and deriving per-class positions and
+    each car's crew/manufacturer. Tolerant of the wider practice/qualifying
+    layouts (missing columns left empty).
+  - `Session.load(results_source=...)` populates `results` from a Classification
+    CSV (otherwise results are derived from the laps).
+- Weather parser & file discovery (milestone 2.7), based on the **verified**
+  real Al Kamel formats (captured via a one-off GitHub Actions probe, since the
+  development sandbox cannot reach the portal):
+  - `alkamel.weather.read_weather`/`to_weather`: parse the Weather CSV
+    (`TIME_UTC_SECONDS;TIME_UTC_STR;AIR_TEMP;TRACK_TEMP;HUMIDITY;PRESSURE;
+    WIND_SPEED;WIND_DIRECTION`) into FastF1-style `weather_data` (`Time`
+    relative to the first sample; `Rainfall` not provided).
+  - `alkamel.discovery`: parse a portal `?season=` page into structured
+    `ResultFile` records (season/event/series/session/hour/kind + URL builder)
+    by reading the embedded `Results/...CSV` paths.
+  - `Session.load(weather_source=...)` populates `weather_data`.
+  - Confirmed the Analysis CSV format (old & modern) and the Classification CSV
+    headers (race `05_`, practice `03_`, qualifying `90_`) against real files.
+- Plotting colour helpers (milestone 2.6):
+  - `plotting.get_class_color` / `get_manufacturer_color` (pure functions
+    returning hex colours, case-insensitive, with a default fallback) plus
+    `list_classes`/`list_manufacturers` and `setup_mpl` (needs the `plot`
+    extra). Colours are organised by class and manufacturer rather than driver.
+
+[Unreleased]: https://github.com/RomainFl50/EndurancePy/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/RomainFl50/EndurancePy/releases/tag/v0.1.0

endurancepy-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,52 @@
+# Code of Conduct
+
+## Our commitment
+
+EndurancePy is an open, welcoming community. We are committed to providing a
+friendly, safe and inclusive environment for everyone who participates —
+contributors, maintainers and users alike — regardless of background or
+experience level.
+
+## Our standards
+
+We expect everyone in the project to:
+
+- Be respectful, considerate and patient.
+- Welcome newcomers and help them get started.
+- Give and accept constructive feedback gracefully.
+- Focus on what is best for the community and the project.
+- Show empathy towards other community members.
+
+Behaviour that makes others feel unwelcome or unsafe is not acceptable and may
+result in removal from project spaces at the maintainers' discretion.
+
+## Adopted standard
+
+This project adopts the **Contributor Covenant, version 2.1**, as its full Code
+of Conduct. Please read the complete text here:
+
+- <https://www.contributor-covenant.org/version/2/1/code_of_conduct/>
+
+It defines the expected standards of behaviour, the responsibilities of
+maintainers, the scope of this policy, and the enforcement guidelines in full.
+
+## Scope
+
+This Code of Conduct applies within all project spaces (the repository, issues,
+pull requests, discussions) and when an individual is representing the project
+in public spaces.
+
+## Reporting
+
+If you experience or witness a problem, please report it privately to the project
+maintainer:
+
+- **Romain Flambard** — romain.flambard@hotmail.fr
+
+All reports will be reviewed and handled confidentially. Maintainers are
+obligated to respect the privacy and security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the
+[Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

endurancepy-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,129 @@
+# Contributing to EndurancePy
+
+First off — thank you for taking the time to contribute! EndurancePy aims to do
+for endurance racing (WEC, ELMS, Asian Le Mans Series, Le Mans Cup, IMSA) what
+[FastF1](https://github.com/theOehrly/Fast-F1) did for Formula 1, and it is very
+much a community effort.
+
+This project is in an **early / design phase** — there is no runnable package
+yet, only the design groundwork. That means there is a lot of high-impact work
+available, and good first contributions are easy to find.
+
+By participating, you agree to abide by our
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+---
+
+## Ways to contribute
+
+- **Code** — implement one of the milestones (parsers, cache, core objects…).
+- **Documentation** — improve docs, examples, docstrings.
+- **Test data** — help build small, shareable fixtures (see the legal note
+  below — do **not** commit raw Al Kamel archives).
+- **Issues** — report bugs, request a series/season, or propose an API design.
+- **Review** — review open pull requests.
+
+If you are unsure where to start, **open an issue** describing what you'd like to
+work on, so we can avoid duplicated effort and agree on the approach before you
+write code.
+
+## Understand the design first
+
+Before writing code, please read the design documents — they are the functional
+and technical spec for the package:
+
+- [`docs/analyse_fastf1.md`](docs/analyse_fastf1.md) — exhaustive inventory of
+  FastF1's content and how each piece maps onto endurance / Al Kamel data.
+- [`docs/plan_implementation.md`](docs/plan_implementation.md) — the
+  implementation plan: package layout, target column schemas, parsing pipeline,
+  derivation algorithms, cache design, milestones and test strategy.
+
+The guiding principle: **mirror FastF1's API and content** wherever the
+underlying public data exists.
+
+## Development setup
+
+> The package skeleton is being bootstrapped; once `pyproject.toml` lands, the
+> setup below applies.
+
+```bash
+# 1. Fork and clone
+git clone https://github.com/<your-username>/EndurancePy.git
+cd EndurancePy
+
+# 2. Create a virtual environment (Python 3.10+)
+python -m venv .venv
+source .venv/bin/activate        # Windows: .venv\Scripts\activate
+
+# 3. Install in editable mode with dev extras
+pip install -e ".[dev]"
+
+# 4. (optional) install pre-commit hooks
+pre-commit install
+```
+
+## Coding guidelines
+
+- **Python 3.10+**, with type hints on public functions.
+- **Formatting & linting**: [`ruff`](https://docs.astral.sh/ruff/)
+  (`ruff format` + `ruff check`).
+- **Type checking**: `mypy`.
+- **Docstrings** on all public classes/functions (NumPy or Google style).
+- **Mirror FastF1 naming** where it makes sense (`get_session`, `Session.load`,
+  `Session.laps`, `pick_*`, `Cache`) so FastF1 users feel at home. Document any
+  deliberate divergence (see the plan).
+- Keep parsers **tolerant**: Al Kamel CSV headers drift across seasons/series —
+  match columns by name, handle the BOM and leading-space header variants.
+
+## Tests
+
+- Use `pytest`. Run the suite with:
+  ```bash
+  pytest
+  ```
+- New parsing logic must come with tests.
+- Prefer **small, synthetic fixtures** that reproduce the format (a couple of
+  cars, two classes, a few laps, a pit stop, a caution period). **Do not commit
+  real Al Kamel timing files** (see the legal note).
+- Network-dependent tests must be marked (e.g. `@pytest.mark.network`) and stay
+  off by default.
+
+## Commit messages
+
+Use clear, descriptive messages. We loosely follow
+[Conventional Commits](https://www.conventionalcommits.org/), e.g.:
+
+```
+feat(alkamel): parse Analysis CSV into Laps
+fix(timeparse): handle the 24: elapsed-time rollover
+docs: clarify per-class position derivation
+test(headers): cover the IMSA WithSections variant
+```
+
+## Pull request workflow
+
+1. Create a topic branch from `main` (`feat/...`, `fix/...`, `docs/...`).
+2. Make focused commits; keep PRs reasonably small and single-purpose.
+3. Ensure `ruff`, `mypy` and `pytest` pass locally.
+4. Fill in the pull request template and link any related issue.
+5. Be responsive to review feedback. Maintainers may request changes before merge.
+
+## ⚖️ Legal note (please read)
+
+EndurancePy parses **publicly published** timing archives. **Al Kamel Systems
+explicitly asserts ownership of its timing data and warns against
+redistribution.** Therefore:
+
+- **Never commit raw Al Kamel data** (CSV/PDF archives) to this repository, and
+  do not bundle or republish it in any artifact.
+- Test fixtures must be **synthetic** or otherwise clearly redistributable.
+- Always respect each site's Terms of Service and `robots.txt`, identify your
+  client honestly, and keep request rates reasonable (the cache exists partly
+  for this reason).
+
+Contributions that redistribute proprietary data will not be accepted.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the
+project's [MIT License](LICENSE).

endurancepy-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Romain Flambard and the EndurancePy 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.