Metadata-Version: 2.1
Name: pypvfs
Version: 1.0.3
Summary: Python bindings for Pinnacle Technology PVFS (virtual filesystem for physiological recordings)
Author: Pinnacle Technology Inc.
License: BSD 3-Clause License
         
         Copyright (c) 2023, Thresa Kelly
         
         Redistribution and use in source and binary forms, with or without
         modification, are permitted provided that the following conditions are met:
         
         1. Redistributions of source code must retain the above copyright notice, this
            list of conditions and the following disclaimer.
         
         2. Redistributions in binary form must reproduce the above copyright notice,
            this list of conditions and the following disclaimer in the documentation
            and/or other materials provided with the distribution.
         
         3. Neither the name of the copyright holder nor the names of its
            contributors may be used to endorse or promote products derived from
            this software without specific prior written permission.
         
         THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
         AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
         IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
         DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
         FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
         DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
         SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
         CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
         OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
         OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
         
Project-URL: Repository, https://github.com/Pinnacle-Technology-Inc/pypvfs
Requires-Python: >=3.10
Requires-Dist: numpy
Requires-Dist: pydantic>=2
Requires-Dist: SQLAlchemy>=2
Requires-Dist: Pillow>=10.0.0
Provides-Extra: video
Requires-Dist: av; extra == "video"
Provides-Extra: test
Requires-Dist: pytest; extra == "test"
Requires-Dist: av; extra == "test"
Provides-Extra: examples
Requires-Dist: pyedflib; extra == "examples"
Requires-Dist: av; extra == "examples"
Description-Content-Type: text/markdown

# pypvfs

**`pypvfs`** is the PyPI distribution name for **Pinnacle Technology PVFS** — a virtual filesystem used for physiological recordings. This is **not** related to the historical HPC “Parallel Virtual File System” or other unrelated “PVFS” acronyms.

After installation you import the **`pvfs_tools`** Python package (same module layout as in the former Morelia monolith):

```bash
pip install pypvfs
```

```python
from pvfs_tools.Core.pvfs_data_file import PvfsDataFile
```

## Optional extras

| Extra | Purpose |
|-------|---------|
| `video` | WebM/VP8 export (`WebMWriter` uses PyAV). `pip install "pypvfs[video]"` |
| `test` | `pytest` + `av` for running the test suite locally |
| `examples` | `pyedflib` + `av` for the Tk GUI EDF and WebM examples |

## Native library

The package ships platform-specific native libraries under `pvfs_tools.Core` (`.dll` on Windows, `.so` on Linux). On PyPI you receive a prebuilt wheel for your platform, so `pip install pypvfs` does **not** require a C++ toolchain.

If you install from source (sdist or a checkout), `pip` will invoke [`scikit-build-core`](https://scikit-build-core.readthedocs.io/) which compiles `src/pvfs_tools/Core/pvfs.cpp` and `pvfs_wrapper.cpp` via CMake. You will need:

- CMake ≥ 3.15 (pip installs `cmake` from PyPI into the isolated build env if your system lacks it)
- A C++17 compiler (`g++`/`clang++` on Linux/macOS, MSVC 2019+ on Windows)

```bash
pip install -e ".[test]"   # builds the native libs and installs in editable mode
pytest
```

## Examples (repository `examples/`)

Requires a working `pypvfs` install; GUI examples need a display.

| Script | Extra deps | Description |
|--------|------------|-------------|
| `examples/pvfs_create_cli.py` | — | CLI to create a synthetic PVFS file |
| `examples/pvfs_to_edf_converter.py` | `pyedflib` | Tk GUI: PVFS → EDF+ |
| `examples/pvfs_to_video_converter.py` | `pypvfs[video]` | Tk GUI: PVFS video → WebM |

```bash
pip install pyedflib
python examples/pvfs_to_edf_converter.py
```

## Documentation

- Quick reference: [docs/pvfsQuickStart.txt](docs/pvfsQuickStart.txt)

## Tests

```bash
pip install -e ".[test]"
pytest
```

## Repository

Source and issues: see **Repository** URL in `pyproject.toml`.

## Publishing releases

Step-by-step (tags, GitKraken, PyPI checks): **[docs/RELEASE.md](docs/RELEASE.md)**.

Do **not** rely on `twine upload` from a developer machine for routine releases (credentials drift and audit pain). Use the GitHub Action instead.

1. **Configure [trusted publishing](https://docs.pypi.org/trusted-publishers/)** on PyPI for this GitHub repository and workflow `publish.yml` (OIDC — no `PYPI_API_TOKEN` in repo secrets unless you choose that path).
2. **Bump** `version` in `pyproject.toml`, commit, then create and push a **version tag** matching your policy, e.g. `v1.0.2`:
   ```bash
   git tag v1.0.2
   git push origin v1.0.2
   ```
   Pushing tag `v*` runs [`.github/workflows/publish.yml`](.github/workflows/publish.yml): [`cibuildwheel`](https://cibuildwheel.pypa.io/) builds a `manylinux_2_28_x86_64` wheel inside the PyPA manylinux Docker image and a `win_amd64` wheel on a Windows runner, then uploads both (plus the sdist) with `pypa/gh-action-pypi-publish`. The manylinux image guarantees a low glibc baseline so the published Linux wheel works on RHEL/CentOS/Rocky/Alma 8+, Ubuntu 20.04+, Debian 11+, and Amazon Linux 2023 — not just the build host.
3. **Manual run:** Actions → **Publish to PyPI** → *Run workflow* (same build/upload path).

**Note:** `ptech-morelia` already uses a similar pattern (tag push + matrix build + OIDC) in its `packaging` workflow — keep both projects on the same release habit so versions stay aligned when you cut coordinated releases.
