pathlib-next 0.4.0__tar.gz → 0.5.0__tar.gz

{pathlib_next-0.4.0 → pathlib_next-0.5.0}/.gitignore

@@ -16,6 +16,9 @@ __pycache__/
 .pytest_cache/
 .mypy_cache/
 .ruff_cache/
+.coverage
+.coverage.*
+htmlcov/
 *.egg-info/
 .venv/
 

pathlib_next-0.5.0/CHANGELOG.md

@@ -0,0 +1,215 @@
+# 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/).
+
+## [Unreleased]
+
+## [0.5.0] - 2026-07-11
+
+### Fixed (critical -- found while writing Phase 6 examples)
+- `Path("...")` -- the top-level dispatcher documented in this project's
+  own README quick start and used throughout -- silently dropped its
+  constructor arguments on Python <3.12, leaving a blank instance that
+  crashed with `AttributeError: _drv` the moment anything touched it (e.g.
+  the `/` operator). Masked on 3.12+, where the real parsing happens in
+  `__init__` (called separately, with the original args, regardless of what
+  `__new__` did) rather than `__new__` itself. Every one of Phase 5's 300
+  tests constructed via `LocalPath(...)` directly instead, so this went
+  undetected until `examples/local_and_mem.py` exercised the documented
+  `Path(...)` entry point end to end.
+
+### Fixed (found by the new Phase 5 test suite, not in the original bug list)
+- `LocalPath.stat()`/`chmod()` inherit directly from `pathlib.Path` via MRO
+  and crashed with `TypeError` on Python 3.9 the moment anything passed
+  `follow_symlinks=` (e.g. `Path.walk()`'s default `follow_symlinks=False`)
+  -- now shimmed with `lstat()`/`lchmod()` on <3.10, same as the existing
+  `FileUri` shim (which now just delegates to `LocalPath`).
+- `MemPath.__init__` decided whether to propagate a parent's backend with
+  `if _backend and backend is None:` -- an empty (but valid) backend dict is
+  falsy, so joining off a freshly-created, empty `MemPath` silently gave the
+  child a disconnected new backend instead of sharing the parent's.
+- `MemPath.stat()` never set `st_size` for files (always defaulted to `0`),
+  breaking any size-based checksum comparison (notably `PathSyncer`'s
+  typical usage).
+- `glob()`'s core algorithm decided whether to recurse into the *parent*
+  directory using whether the *leaf* segment is a wildcard, instead of
+  whether the *parent path itself* contains one. Since a wildcarded leaf
+  with a literal parent directory is the overwhelmingly common case
+  (`glob("*.py")`), this always took the "recurse into parent" branch,
+  which only degenerated back to the correct single directory when the
+  parent has a non-empty literal name to re-match against -- true for
+  essentially every real filesystem path except an OS root. It silently
+  returned the wrong result on `MemPath`'s virtual root (empty name).
+- `HttpPath.iterdir()` gave every subdirectory entry an empty `.name`:
+  directory-listing entries for subdirectories carry a trailing `/`
+  (`htmllistparse`'s convention), which wasn't stripped before building the
+  child's path, and `Pathname.name` derives from the last path segment --
+  empty for a trailing-slash path.
+- `SftpPath.rename()` resolved a plain string target relative to `self`
+  (joining it as a child, e.g. `"/a.txt".rename("b.txt")` produced
+  `"/a.txt/b.txt"`) instead of `self`'s parent (sibling rename).
+
+### Added (test suite)
+- Full pytest suite (`tests/`): pure-path parity against `pathlib.PurePosixPath`
+  (`test_parity_pure.py`), local I/O parity against `pathlib.Path`/`os.walk`
+  (`test_parity_io.py`), a reusable filesystem-contract mixin run against
+  `LocalPath`/`MemPath`/`FileUri` and exported as `pathlib_next.testing.
+  PathContract` for third-party `Path`/`UriPath` implementers
+  (`test_contract.py`), glob vs. stdlib ground truth (`test_glob.py`), URI
+  parsing/scheme-dispatch/query/source coverage, MemPath- and SFTP-specific
+  unit tests (SFTP mocked, no real server), HTTP tests against a real stdlib
+  `ThreadingHTTPServer`, and `PathSyncer` coverage. 300 tests, ~85% line
+  coverage, green on both Python 3.9 and 3.13.
+
+### Added (docs)
+- `docs/guides/schemes.md` (capability matrix per scheme) and
+  `docs/guides/extending.md` (both extension tracks, with worked examples
+  and `pathlib_next.testing.PathContract` usage). Rewrote `docs/index.md`
+  and the README with a 30-second example per scheme and a capability
+  matrix. Class-level docstrings added across the package for the rendered
+  API reference.
+
+### Changed
+- `examples/example.py` (an unstructured scratch script) split into three
+  focused, runnable examples: `examples/local_and_mem.py` (self-contained,
+  no network), `examples/http_listing.py` and `examples/sftp_sync.py`
+  (network-touching, guarded under `if __name__ == "__main__"`,
+  configurable via env vars, fail soft when unreachable/unconfigured).
+
+### Added
+- `Pathname.joinpath()`, `Pathname.full_match()` (3.13 parity, supports `**`
+  matching any number of segments), `Pathname.anchor`/`drive`/`root`
+  (generic derivation for non-local paths), `Path.rglob()`,
+  `read_text(..., newline=)` (3.13 parity), `Path.samefile()` (default
+  `st_dev`/`st_ino` comparison when the backend's `stat()` provides them,
+  `NotImplementedError` otherwise).
+- `Path.glob()`/`LocalPath.glob()`: `recursive=` now auto-detects (`True` if
+  the pattern has a `"**"` component) instead of defaulting to `False`;
+  explicit `recursive=True`/`False` still overrides.
+- `Path.copy()`: raises `IsADirectoryError` when the target is an existing
+  directory (previously misbehaved); gained `follow_symlinks=`/
+  `preserve_metadata=` kwargs, named to match CPython 3.14's `Path.copy()`.
+- `docs/divergences.md`: registry of every deliberate behavioral divergence
+  from `pathlib`, with rationale. Linked from the docs nav.
+
+### Fixed
+- `Path.mkdir(parents=True)` created intermediate parents with `exist_ok=False`
+  (racy, and wrong when a parent already existed) and dropped the caller's
+  `exist_ok` on the final retry.
+- `Path.touch(exist_ok=False)` silently truncated an existing file instead of
+  raising `FileExistsError` (pathlib parity).
+- `LocalPath.glob()`'s `dironly` parameter defaulted to `False`, which made the
+  `is None` check for trailing-slash directory-only detection dead code.
+- `Stat._st_mode()` only caught `FileNotFoundError`, letting `PermissionError`
+  and other `OSError`s propagate out of `exists()`/`is_dir()`/etc. where pathlib
+  returns `False`. Also fixed: `follow_symlinks` was accepted but never
+  forwarded to the underlying `stat()` call, so `is_symlink()` never actually
+  inspected the symlink itself.
+- `MemPath._open()` treated any mode other than `"w"` as a read, so `"a"`/`"x"`
+  silently misbehaved; now dispatches `r`/`w`/`x`/`a` correctly and raises
+  `NotImplementedError` for anything else. `MemBytesIO.close()` used
+  `seek(0);read()` instead of `getvalue()`, losing content if the caller's
+  cursor wasn't already at position 0 when closing.
+- `MemPath.normalized` mangled `".."`-escaping paths (e.g. `".."`) into `"."`;
+  now normalizes against a virtual root so they clamp at the root instead.
+- `PathAndStat.__getattr__()` returned `None` for any unrecognized attribute
+  instead of raising `AttributeError`, breaking `hasattr()`-based logic.
+- `parsedate(None)` / an unparseable date string returned "now" instead of
+  epoch 0, which could poison `PathSyncer`'s checksum/freshness comparisons for
+  HTTP sources with no `Last-Modified` header.
+- `HttpPath.stat()` used a bare `except:`; cached `_isdir` from a response that
+  hadn't been confirmed successful yet (including 404s); and didn't fall back
+  to GET when a server rejected `HEAD` with 405.
+- `uri.Query` no longer depends on `uritools`' private `_querydict`/`_querylist`
+  helpers (reimplemented locally against the public `uriencode()`).
+- `Uri` join (`_load_parts`): `query`/`fragment` are now resolved with the same
+  "last segment that actually sets one wins" rule already used for `source`
+  (previously any segment, even one with no query/fragment, would blank out an
+  earlier segment's). Join semantics are now documented explicitly:
+  pathlib-`joinpath`-like, not RFC 3986 reference resolution, `..` is never
+  resolved during join.
+- `Source.is_local()` (DNS lookup) and `get_machine_ips()` are now
+  `functools.lru_cache`d -- previously ran on every call.
+
+### Fixed (crash-level bugs)
+- `MemPath.stat()`/`MemPath._open()` returned a `FileNotFoundError` instance instead
+  of raising it for a missing path, causing an unrelated `AttributeError` downstream.
+- `LRU.invalidate()` called `self.lock()` instead of using `self.lock` as a context
+  manager (`RLock` isn't callable) -- broke the SFTP client reconnect path.
+- `Pathname.match()` had reversed `isinstance()` arguments and compared against
+  `str(self)` (which includes scheme/host for `Uri`) instead of `as_posix()`.
+- Glob wildcard detection (`WILCARD_PATTERN`, renamed `WILDCARD_PATTERN`, old name
+  kept as an alias) used `.match()` (anchored) instead of `.search()`, so patterns
+  like `"foo*"` weren't recognized as wildcards.
+- `Uri` was unhashable (defined `__eq__` without `__hash__`); `__eq__` now also
+  returns `NotImplemented` for non-`Pathname`/`str` operands instead of raising.
+- `Uri.is_relative_to()` used `str.startswith()` on normalized path strings, so
+  `/foo/bar2` was incorrectly reported as relative to `/foo/bar`; now compares
+  path segments.
+- `Uri.relative_to(walk_up=True)` was dead code -- an early guard raised
+  `ValueError` before the walk-up loop ever ran.
+- `HttpPath.is_dir()`/`is_file()` tested truthiness of bound methods
+  (`self._is_dir`, `self.is_dir`) instead of calling/checking the right attribute,
+  so both always returned truthy nonsense.
+- `SftpPath.chmod()` didn't accept `follow_symlinks=`, so the inherited `lchmod()`
+  crashed with `TypeError`; now raises `NotImplementedError` for
+  `follow_symlinks=False` (paramiko has no `lchmod`).
+- `SftpPath` defined `_rename()`, which nothing ever called -- renamed to
+  `rename()` so `move()`/`rename()` actually use SFTP's native rename instead of
+  silently falling back to copy+unlink for every move.
+- `Uri.__init__()` used a bare `except:` around `Path.as_uri()` (now
+  `except ValueError:`, matching what `as_uri()` actually raises for relative
+  paths) and crashed with `AttributeError` when constructing from an
+  `os.PathLike` that only implements `__fspath__` (no `as_posix()`).
+- `Path.rm(ignore_error=callable)` never actually called the callable -- both
+  branches of its error handler returned the callable object itself.
+
+### Fixed (Python 3.9/3.10 compatibility)
+- Actual Python 3.9/3.10 runtime compatibility (CI previously only tested 3.11/3.13
+  and missed these): `LocalPath`/`Uri` case-sensitivity and path-separator detection
+  crashed on 3.9-3.11 (`_flavour` object has no `normcase`); `open(mode="r")` crashed
+  on <3.10 (`io.text_encoding` is 3.10+); glob pattern compilation crashed on <3.11
+  (`re.NOFLAG` is 3.11+); `FileUri.stat()`/`chmod()` crashed on 3.9
+  (`pathlib.Path.stat/chmod` gained `follow_symlinks=` in 3.10; raises
+  `NotImplementedError` there for `follow_symlinks=False`).
+- `LocalPath._path_separators` returned the env-var list separator (`;`/`:`) instead
+  of the path separator, and could include a `None` altsep on POSIX.
+
+### Added
+- `tests/test_smoke.py`: regression coverage for README/example snippets across
+  supported Python versions.
+
+## [0.4.1] - 2026-07-11
+
+### Fixed
+- Removed explicit `[tool.hatch.build.targets.wheel]` packages config that caused hatchling to fail resolving `README.md` during editable installs on CI.
+- Converted `README.md` from a symlink (mode `120000`) to a regular file, fixing `git checkout` failures on macOS and Windows runners.
+- Removed agent-tooling references (`AGENTS.md`, `PYTHON.md`) from committed files.
+
+## [0.4.0] - 2026-07-11
+
+### Added
+- Standardized repository layout and relocated examples to `examples/` directory.
+- Configured MkDocs documentation site with dynamic API reference using `mkdocstrings`.
+- Added GitHub Actions workflows for matrix testing (`test.yml`) and release pipelines (`release.yml`).
+- Added typing marker `py.typed` for PEP 561 compliance.
+
+### Changed
+- Added backward compatibility support for Python 3.9 and 3.10: added `from __future__ import annotations` across the codebase, refactored runtime-evaluated union types to use `typing.Union`, and provided fallbacks for `TypeAlias` and `ParamSpec`.
+- Updated package requirement to `requires-python = ">=3.9"`.
+
+## [0.3.5] - 2026-07-11
+
+### Added
+- Split path into protocols that can be standalone.
+- Sync error handling.
+- Generic Path Protocol based pathlib implementation for URI paths with file access support for sftp, http, file schemes.
+
+[Unreleased]: https://github.com/jose-pr/pathlib_next/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/jose-pr/pathlib_next/compare/v0.4.1...v0.5.0
+[0.4.1]: https://github.com/jose-pr/pathlib_next/compare/v0.4.0...v0.4.1
+[0.4.0]: https://github.com/jose-pr/pathlib_next/releases/tag/v0.4.0
+[0.3.5]: https://github.com/jose-pr/pathlib_next/releases/tag/v0.3.5

pathlib_next-0.5.0/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: pathlib_next
+Version: 0.5.0
+Summary: Generic Path Protocol based pathlib
+Project-URL: Homepage, https://github.com/jose-pr/pathlib_next/
+Project-URL: Documentation, https://jose-pr.github.io/pathlib_next/
+Project-URL: Issues, https://github.com/jose-pr/pathlib_next/issues
+Author: Jose A
+License-File: LICENSE
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.9
+Provides-Extra: dev
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: hatchling; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: twine; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocs; extra == 'docs'
+Requires-Dist: mkdocs-material; extra == 'docs'
+Requires-Dist: mkdocstrings[python]; extra == 'docs'
+Provides-Extra: http
+Requires-Dist: bs4; extra == 'http'
+Requires-Dist: htmllistparse; extra == 'http'
+Requires-Dist: requests; extra == 'http'
+Requires-Dist: uritools; extra == 'http'
+Provides-Extra: sftp
+Requires-Dist: paramiko; extra == 'sftp'
+Requires-Dist: uritools; extra == 'sftp'
+Provides-Extra: uri
+Requires-Dist: uritools; extra == 'uri'
+Description-Content-Type: text/markdown
+
+# pathlib_next
+
+[![Version](https://img.shields.io/pypi/v/pathlib_next.svg)](https://pypi.org/project/pathlib_next/)
+[![Python versions](https://img.shields.io/pypi/pyversions/pathlib_next.svg)](https://pypi.org/project/pathlib_next/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+[![Docs](https://img.shields.io/badge/docs-latest-blue.svg)](https://jose-pr.github.io/pathlib_next/)
+[![CI](https://img.shields.io/github/actions/workflow/status/jose-pr/pathlib_next/test.yml)](https://github.com/jose-pr/pathlib_next/actions/workflows/test.yml)
+
+A **robust, extensible pathlib-like base** for any resource addressable as a
+path or URI. Same method names, signatures, semantics, and exception types as
+`pathlib.Path` wherever a `pathlib.Path` equivalent exists -- write code once
+against `Path`/`UriPath` and it works against your local disk, an in-memory
+tree, an HTTP index, or an SFTP server. Every intentional divergence from
+`pathlib`'s behavior is documented, not silent -- see
+[`docs/divergences.md`](https://jose-pr.github.io/pathlib_next/divergences/).
+
+## Features
+
+| Capability | `LocalPath` | `file:` | `mem:` (`MemPath`) | `http(s):` | `sftp:` |
+| --- | --- | --- | --- | --- | --- |
+| Read | Yes | Yes | Yes | Yes | Yes |
+| Write | Yes | Yes | Yes | No | Yes |
+| List (`iterdir`) | Yes | Yes | Yes | Yes (HTML index) | Yes |
+| Stat / exists / is_dir / is_file | Yes | Yes | Yes | Yes | Yes |
+| `mkdir` | Yes | Yes | Yes | No | Yes |
+| Delete | Yes | Yes | Yes | No | Yes |
+| `rename` | Yes | Yes | No (copy+unlink fallback) | No | Yes |
+| Extra required | none | none | none | `http` | `sftp` |
+
+Every scheme shares the same `glob()`, `walk()`, `copy()`/`move()`, `rm()`
+implementations -- see the full matrix and notes in
+[Schemes](https://jose-pr.github.io/pathlib_next/guides/schemes/).
+
+- **Unified path interface** across local files, in-memory paths, and
+  `sftp`/`http`/`file` URIs.
+- **`MemPath`** -- a lightweight virtual filesystem for mocks, tests, or
+  transient storage.
+- **`PathSyncer`** -- one-way checksum-driven tree sync between any two
+  `Path` implementations, with dry-run and event hooks.
+- **`Query`/`Source`** -- parse and serialize URL query strings and URI
+  authority components.
+- **Extensible two ways**: subclass `Path` directly for a custom
+  non-URI resource, or subclass `UriPath` for a new URI scheme -- see
+  [Extending](https://jose-pr.github.io/pathlib_next/guides/extending/).
+
+## Installation
+
+```bash
+pip install pathlib_next
+```
+
+Optional features/extras:
+
+| Extra/flag | Adds | Needed for |
+| --- | --- | --- |
+| `uri` | `uritools` | URI parsing capabilities |
+| `http` | `requests`, `bs4`, `htmllistparse` | Read and list files over HTTP/HTTPS |
+| `sftp` | `paramiko` | SFTP path operations and transfers |
+
+`import pathlib_next` and `LocalPath`/`MemPath` work with no extras
+installed.
+
+## Quick start
+
+**Local filesystem** -- drop-in `pathlib.Path`:
+
+```python
+from pathlib_next import Path
+
+p = Path("./data") / "report.txt"
+p.write_text("hello")
+print(p.read_text())
+```
+
+**In-memory** (`mem:`) -- a virtual filesystem, no disk I/O:
+
+```python
+from pathlib_next.mempath import MemPath
+
+p = MemPath("/config/settings.json")
+p.parent.mkdir(parents=True, exist_ok=True)
+p.write_text('{"debug": true}')
+```
+
+**`file:`** -- the same local filesystem, addressed as a URI:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("file:./data/report.txt")
+print(p.read_text())
+```
+
+**`http(s):`** -- read files and list Apache/nginx-style directory indexes:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("http://example.com/data/")
+for child in p.iterdir():
+    if child.is_file():
+        print(child.name, child.stat().st_size)
+```
+
+**`sftp:`** -- same interface, over SSH:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("sftp://user@host/var/log/app.log")
+print(p.read_text())
+```
+
+## Extending
+
+Two first-class ways to add a new path-addressable resource -- both covered
+in depth, with worked examples, in
+[Extending](https://jose-pr.github.io/pathlib_next/guides/extending/):
+
+- Subclass `Path` directly for a custom, non-URI resource (`MemPath` is the
+  reference exemplar).
+- Subclass `UriPath` and set `__SCHEMES` for a new URI scheme (`FileUri`/
+  `HttpPath`/`SftpPath` are the built-in examples).
+
+`pathlib_next.testing.PathContract` is a reusable pytest mixin covering the
+baseline contract every implementation must satisfy -- subclass it with a
+`root` fixture to verify your own.
+
+## API overview
+
+| Module/Package | Purpose |
+| --- | --- |
+| `pathlib_next.path` | Base Path implementation and protocols |
+| `pathlib_next.uri` | URI/URL specific path support and Query utils |
+| `pathlib_next.mempath` | In-memory transient path structure |
+| `pathlib_next.utils.sync` | Synchronization functions and PathSyncer class |
+| `pathlib_next.testing` | `PathContract`, a pytest mixin for verifying custom implementations |
+
+## Supported Python versions
+
+Python >= 3.9, tested on 3.9 and 3.13 in CI (see
+[`.github/workflows/test.yml`](.github/workflows/test.yml)).
+
+## Development
+
+```bash
+pip install -e ".[dev,uri,http,sftp]"
+pytest -q
+```
+
+If you maintain separate virtual environments per Python version locally
+(e.g. `.venv/3.9/`, `.venv/3.13/`), run the same `pytest -q` in each --
+CI does the equivalent across Python 3.9/3.13 on Linux, macOS, and Windows.
+
+### Releasing
+
+This project follows [Semantic Versioning](https://semver.org/) and keeps a
+[`CHANGELOG.md`](CHANGELOG.md). Pushing a tag matching `v*` triggers the release
+workflow: test gate → build → publish → docs deploy.
+
+### Documentation site
+
+MkDocs builds the API reference from `docs/`, published on every
+release. To preview locally: `mkdocs serve`.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

pathlib_next-0.5.0/README.md

@@ -0,0 +1,168 @@
+# pathlib_next
+
+[![Version](https://img.shields.io/pypi/v/pathlib_next.svg)](https://pypi.org/project/pathlib_next/)
+[![Python versions](https://img.shields.io/pypi/pyversions/pathlib_next.svg)](https://pypi.org/project/pathlib_next/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+[![Docs](https://img.shields.io/badge/docs-latest-blue.svg)](https://jose-pr.github.io/pathlib_next/)
+[![CI](https://img.shields.io/github/actions/workflow/status/jose-pr/pathlib_next/test.yml)](https://github.com/jose-pr/pathlib_next/actions/workflows/test.yml)
+
+A **robust, extensible pathlib-like base** for any resource addressable as a
+path or URI. Same method names, signatures, semantics, and exception types as
+`pathlib.Path` wherever a `pathlib.Path` equivalent exists -- write code once
+against `Path`/`UriPath` and it works against your local disk, an in-memory
+tree, an HTTP index, or an SFTP server. Every intentional divergence from
+`pathlib`'s behavior is documented, not silent -- see
+[`docs/divergences.md`](https://jose-pr.github.io/pathlib_next/divergences/).
+
+## Features
+
+| Capability | `LocalPath` | `file:` | `mem:` (`MemPath`) | `http(s):` | `sftp:` |
+| --- | --- | --- | --- | --- | --- |
+| Read | Yes | Yes | Yes | Yes | Yes |
+| Write | Yes | Yes | Yes | No | Yes |
+| List (`iterdir`) | Yes | Yes | Yes | Yes (HTML index) | Yes |
+| Stat / exists / is_dir / is_file | Yes | Yes | Yes | Yes | Yes |
+| `mkdir` | Yes | Yes | Yes | No | Yes |
+| Delete | Yes | Yes | Yes | No | Yes |
+| `rename` | Yes | Yes | No (copy+unlink fallback) | No | Yes |
+| Extra required | none | none | none | `http` | `sftp` |
+
+Every scheme shares the same `glob()`, `walk()`, `copy()`/`move()`, `rm()`
+implementations -- see the full matrix and notes in
+[Schemes](https://jose-pr.github.io/pathlib_next/guides/schemes/).
+
+- **Unified path interface** across local files, in-memory paths, and
+  `sftp`/`http`/`file` URIs.
+- **`MemPath`** -- a lightweight virtual filesystem for mocks, tests, or
+  transient storage.
+- **`PathSyncer`** -- one-way checksum-driven tree sync between any two
+  `Path` implementations, with dry-run and event hooks.
+- **`Query`/`Source`** -- parse and serialize URL query strings and URI
+  authority components.
+- **Extensible two ways**: subclass `Path` directly for a custom
+  non-URI resource, or subclass `UriPath` for a new URI scheme -- see
+  [Extending](https://jose-pr.github.io/pathlib_next/guides/extending/).
+
+## Installation
+
+```bash
+pip install pathlib_next
+```
+
+Optional features/extras:
+
+| Extra/flag | Adds | Needed for |
+| --- | --- | --- |
+| `uri` | `uritools` | URI parsing capabilities |
+| `http` | `requests`, `bs4`, `htmllistparse` | Read and list files over HTTP/HTTPS |
+| `sftp` | `paramiko` | SFTP path operations and transfers |
+
+`import pathlib_next` and `LocalPath`/`MemPath` work with no extras
+installed.
+
+## Quick start
+
+**Local filesystem** -- drop-in `pathlib.Path`:
+
+```python
+from pathlib_next import Path
+
+p = Path("./data") / "report.txt"
+p.write_text("hello")
+print(p.read_text())
+```
+
+**In-memory** (`mem:`) -- a virtual filesystem, no disk I/O:
+
+```python
+from pathlib_next.mempath import MemPath
+
+p = MemPath("/config/settings.json")
+p.parent.mkdir(parents=True, exist_ok=True)
+p.write_text('{"debug": true}')
+```
+
+**`file:`** -- the same local filesystem, addressed as a URI:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("file:./data/report.txt")
+print(p.read_text())
+```
+
+**`http(s):`** -- read files and list Apache/nginx-style directory indexes:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("http://example.com/data/")
+for child in p.iterdir():
+    if child.is_file():
+        print(child.name, child.stat().st_size)
+```
+
+**`sftp:`** -- same interface, over SSH:
+
+```python
+from pathlib_next.uri import UriPath
+
+p = UriPath("sftp://user@host/var/log/app.log")
+print(p.read_text())
+```
+
+## Extending
+
+Two first-class ways to add a new path-addressable resource -- both covered
+in depth, with worked examples, in
+[Extending](https://jose-pr.github.io/pathlib_next/guides/extending/):
+
+- Subclass `Path` directly for a custom, non-URI resource (`MemPath` is the
+  reference exemplar).
+- Subclass `UriPath` and set `__SCHEMES` for a new URI scheme (`FileUri`/
+  `HttpPath`/`SftpPath` are the built-in examples).
+
+`pathlib_next.testing.PathContract` is a reusable pytest mixin covering the
+baseline contract every implementation must satisfy -- subclass it with a
+`root` fixture to verify your own.
+
+## API overview
+
+| Module/Package | Purpose |
+| --- | --- |
+| `pathlib_next.path` | Base Path implementation and protocols |
+| `pathlib_next.uri` | URI/URL specific path support and Query utils |
+| `pathlib_next.mempath` | In-memory transient path structure |
+| `pathlib_next.utils.sync` | Synchronization functions and PathSyncer class |
+| `pathlib_next.testing` | `PathContract`, a pytest mixin for verifying custom implementations |
+
+## Supported Python versions
+
+Python >= 3.9, tested on 3.9 and 3.13 in CI (see
+[`.github/workflows/test.yml`](.github/workflows/test.yml)).
+
+## Development
+
+```bash
+pip install -e ".[dev,uri,http,sftp]"
+pytest -q
+```
+
+If you maintain separate virtual environments per Python version locally
+(e.g. `.venv/3.9/`, `.venv/3.13/`), run the same `pytest -q` in each --
+CI does the equivalent across Python 3.9/3.13 on Linux, macOS, and Windows.
+
+### Releasing
+
+This project follows [Semantic Versioning](https://semver.org/) and keeps a
+[`CHANGELOG.md`](CHANGELOG.md). Pushing a tag matching `v*` triggers the release
+workflow: test gate → build → publish → docs deploy.
+
+### Documentation site
+
+MkDocs builds the API reference from `docs/`, published on every
+release. To preview locally: `mkdocs serve`.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

pathlib_next-0.5.0/docs/divergences.md

@@ -0,0 +1,61 @@
+# Divergences from `pathlib`
+
+`pathlib_next` targets `pathlib.Path` parity: same method names, signatures,
+semantics and exception types wherever a `pathlib.Path` equivalent exists.
+Extensions (extra optional kwargs, new methods like `rm()`/`sync`) are
+allowed. Any *behavioral* divergence from `pathlib` on a method that exists
+in both must be listed here -- no silent divergence.
+
+`LocalPath` is `pathlib.WindowsPath`/`pathlib.PosixPath` with our `Path` mixed
+in via MRO, so unless noted otherwise it behaves exactly like `pathlib.Path`
+(it inherits the real implementation for anything not explicitly overridden).
+The divergences below apply to `Uri`/`UriPath` and `MemPath`.
+
+| Method | pathlib behavior | Our behavior | Why |
+| --- | --- | --- | --- |
+| `Uri("a").parent` | `PurePosixPath("a").parent == PurePosixPath(".")` | `Uri("a").parent` has path `""` (`Uri("")`, which round-trips) | `Uri` has no cwd-relative concept of `"."` -- an empty path is the URI-natural "no path" representation. Changing this would make `Uri("")` non-idempotent under `.parent`. |
+| `with_name()` / `with_suffix()` / `with_stem()` on `Uri`/`UriPath` | N/A (pathlib has no query/fragment) | Preserve the URI's query and fragment (implemented via `with_path`, which carries them over) | Deliberate extension: `UriPath("http://h/a?x=1").with_suffix(".txt")` keeping `?x=1` matches how most callers actually want to retarget just the path component of a URL. **User decision, 2026-07-11.** |
+| `Path.__iter__` | `pathlib.Path` is not iterable (no `__iter__`) | `iter(path)` is `path.iterdir()` | Deliberate extension for ergonomic `for child in path:` loops. **Caution:** on remote schemes (http/sftp) this is a network call. **User decision, 2026-07-11.** |
+| `Path.copy(target, ...)` | CPython 3.14 `Path.copy(target, *, follow_symlinks=True, dirs_exist_ok=False, preserve_metadata=False)`; always raises if `target` exists | Ours predates 3.14. Signature: `copy(target, *, overwrite=False, follow_symlinks=True, preserve_metadata=True)`. `overwrite=True` unlinks an existing non-directory target first; `preserve_metadata` defaults to **True** (opposite of 3.14) and only propagates `st_mode`, not timestamps/xattrs | Argument names aligned with 3.14 where cheap; `preserve_metadata=True` default kept for backward compat with this method's pre-existing (pre-3.14-alignment) behavior of always copying the mode bits. Full metadata preservation (timestamps, xattrs) is not implemented. |
+| `Path.move(target, ...)` | Not in `pathlib` at all | Our own extension: tries `rename()`, falls back to copy+unlink | N/A -- pure extension, no pathlib method to diverge from. |
+| `Path.rm(recursive=, missing_ok=, ignore_error=)` | Not in `pathlib` (closest: `shutil.rmtree`) | Our own extension | N/A -- pure extension. |
+| `PathSyncer` / `Query` / `Source` | N/A | Our own extensions | N/A -- pure extensions, no pathlib equivalent. |
+
+## Explicitly out of scope (not implemented on `Pathname`/`Path`)
+
+These `pathlib.Path` methods are **not** part of the generic `Pathname`/`Path`
+contract because they don't have a portable meaning across arbitrary
+URI/virtual backends (a `MemPath` or `http://` URL has no filesystem-relative
+cwd, no symlinks, no OS-level owner/group). `LocalPath` gets every one of
+these for free from `pathlib.Path` via MRO -- this list only describes what
+`Uri`/`UriPath`/`MemPath` (and custom `Path` subclasses in general) don't get:
+
+- `resolve()`, `absolute()` -- no portable notion of "the current working
+  directory" or canonicalizing `..`/symlinks for an arbitrary backend.
+- `readlink()`, `symlink_to()`, `hardlink_to()` -- no portable symlink/hardlink
+  concept (sftp *could* support these via paramiko, but it's not implemented).
+- `owner()`, `group()` -- no portable uid/gid-to-name mapping.
+- `expanduser()`, `Path.cwd()`, `Path.home()` -- inherently tied to the local
+  OS/filesystem, meaningless for a URI or in-memory path.
+- `walk(..., follow_symlinks=True)` symlink-cycle protection -- `walk()`
+  itself is implemented (see `Path.walk`), but cycle detection when following
+  symlinks is not; only `LocalPath` (via pathlib) protects against symlink
+  loops during a followed walk.
+
+## Deliberate extensions (new methods/kwargs, not divergences)
+
+These don't diverge from any existing pathlib behavior (pathlib has no
+equivalent, or the kwarg is new/optional) -- listed for completeness, not
+because a behavioral decision needed documenting:
+
+- `joinpath(*args)`, `rglob(pattern)`, `full_match(pattern)` (3.13 parity),
+  `anchor`/`drive`/`root` on `Pathname` (generic derivation: `root` is `"/"`
+  when the first segment is empty, else `""`; `drive` is always `""`),
+  `read_text(..., newline=)` (3.13 parity) -- all additive, no divergence.
+- `Path.glob()`/`LocalPath.glob()`: `recursive=` defaults to auto-detect
+  (`True` if the pattern contains a `"**"` component, else `False`) instead
+  of pathlib's implicit-always-recursive-on-`**` with no override. Passing
+  `recursive=False`/`True` explicitly always wins over the auto-detect.
+  **User decision, 2026-07-11.** `include_hidden=`/`dironly=` are documented
+  extensions beyond pathlib's `glob()` signature. **Caution:** on remote
+  schemes (http/sftp), a recursive glob walks the whole remote subtree.