pathlib-next 0.8.0__tar.gz → 0.8.1__tar.gz

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/CHANGELOG.md

@@ -7,6 +7,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.8.1] - 2026-07-16
+
+### Fixed
+- **`LocalPath.walk()`/`rm()` raised `TypeError: cannot unpack non-iterable
+  DirEntry object` on Python 3.11/3.12.** Those stdlib versions define their
+  own `pathlib.Path._scandir()` (returning raw `os.scandir()` `DirEntry`
+  objects), which sits ahead of this project's `_scandir()` in `LocalPath`'s
+  MRO and silently shadowed it -- breaking the `(name, FileStat|None)`
+  contract `walk()`/`glob()`/`rm()` expect. `LocalPath` now defines its own
+  `_scandir()` explicitly, reusing each `DirEntry`'s cached `lstat()` so the
+  perf win from `_scandir()` unification is preserved. On 3.12+, stdlib
+  `pathlib.Path` also defines its own `walk()` ahead of ours in the MRO, and
+  that stdlib `walk()` treats `self._scandir()`'s return value as a context
+  manager (`with scandir_it:`) -- our own `_scandir()` is a plain generator,
+  so stdlib's `walk()` raised `TypeError: 'generator' object does not
+  support the context manager protocol` even with the override above.
+  `LocalPath` now also overrides `walk()` explicitly, routing to this
+  project's own implementation regardless of Python version. Introduced in
+  0.8.0 (`8cdbefa`), exposed on the CI 3.11/3.12 legs.
+- **`Test No-Extras` CI job was red.** `tests/test_smoke.py` unconditionally
+  constructed an `http://`/`sftp://` `UriPath` in two tests, requiring
+  `requests`/`paramiko` even though the no-extras job installs neither; a
+  third test wrongly assumed `S3Path` requires `boto3` to register (it only
+  needs `botocore`, imported lazily inside a method). The two hard tests now
+  `pytest.importorskip` their extra; the `S3Path` check now probes for
+  `botocore`. Introduced in 0.8.0 (`94bd545`/`8cdbefa`), fixed with the
+  expected skip count (2) verified in a real no-extras venv.
+- **Importable on a clean Python 3.9 install.** `pathlib_next.utils` used
+  `typing.ParamSpec` (3.10+), falling back to `typing_extensions.ParamSpec` and
+  then to a bare `typing.TypeVar`. A `TypeVar` has no `.args`, so the
+  `*args: K.args` annotations raised `AttributeError: 'TypeVar' object has no
+  attribute 'args'` at import time, making `import pathlib_next` fail on 3.9
+  whenever `typing_extensions` was absent. Since `typing_extensions` is not a
+  runtime dependency, this broke a plain `pip install pathlib_next` on 3.9. The
+  final fallback is now a minimal `ParamSpec` shim providing `.args`/`.kwargs`,
+  so no runtime dependency is added and 3.10+ keeps using `typing.ParamSpec`
+  unchanged.
+
 ## [0.8.0] - 2026-07-13
 
 ### Added
@@ -437,7 +475,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
 - 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.7.0...HEAD
+[Unreleased]: https://github.com/jose-pr/pathlib_next/compare/v0.8.1...HEAD
+[0.8.1]: https://github.com/jose-pr/pathlib_next/compare/v0.8.0...v0.8.1
+[0.8.0]: https://github.com/jose-pr/pathlib_next/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/jose-pr/pathlib_next/compare/v0.6.0...v0.7.0
 [0.6.0]: https://github.com/jose-pr/pathlib_next/compare/v0.5.0...v0.6.0
 [0.5.0]: https://github.com/jose-pr/pathlib_next/compare/v0.4.1...v0.5.0

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pathlib_next
-Version: 0.8.0
+Version: 0.8.1
 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/

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pathlib_next"
-version = "0.8.0"
+version = "0.8.1"
 authors = [{ name = "Jose A" }]
 description = "Generic Path Protocol based pathlib"
 readme = "README.md"

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/src/pathlib_next/fspath.py

@@ -11,6 +11,7 @@ import types as _types
 import typing as _ty
 
 from . import path as _proto
+from .utils.stat import FileStat as _FileStat
 
 # pathlib.Path.stat()/chmod() only accept follow_symlinks= on 3.10+; below
 # that, LocalPath (which inherits them directly from pathlib.Path via MRO,
@@ -84,6 +85,36 @@ class LocalPath(
 
     __slots__ = ()
 
+    def _scandir(self):
+        # On 3.11+, `pathlib.Path._scandir()` (stdlib, ahead of ours in the
+        # MRO via WindowsPath/PosixPath) shadows `_proto.Path._scandir()`
+        # and returns `os.scandir(self)` directly -- an iterator of raw
+        # `os.DirEntry`, not this project's `(name, FileStat|None)` tuples.
+        # walk()/glob() expect the latter, so re-assert our own contract
+        # here regardless of what stdlib does in a given version. DirEntry's
+        # own cached lstat (`follow_symlinks=False`, matching walk()'s
+        # default) is reused instead of a fresh stat() round trip.
+        for entry in _os.scandir(self):
+            try:
+                stat = _FileStat.from_stat(entry.stat(follow_symlinks=False))
+            except OSError:
+                stat = None
+            yield entry.name, stat
+
+    def walk(self, top_down=True, on_error=None, follow_symlinks=False):
+        # 3.12+ stdlib `pathlib.Path.walk()` sits ahead of ours in the MRO
+        # and would otherwise win here. Its implementation calls
+        # `self._scandir()` expecting stdlib's own context-manager-capable
+        # `os.scandir(self)` return value ("with scandir_it:") -- our
+        # `_scandir()` override above is a plain generator, so stdlib's
+        # `walk()` breaks on it (`TypeError: 'generator' object does not
+        # support the context manager protocol`). Route explicitly to our
+        # own `walk()` (which drives `_scandir()` correctly) regardless of
+        # which one the MRO would otherwise resolve to.
+        return _proto.Path.walk(
+            self, top_down=top_down, on_error=on_error, follow_symlinks=follow_symlinks
+        )
+
     def stat(self, *, follow_symlinks=True):
         # pathlib.Path.stat() (next in MRO via WindowsPath/PosixPath) only
         # accepts follow_symlinks= on 3.10+; below that, lstat() is the

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/src/pathlib_next/utils/__init__.py

@@ -6,12 +6,29 @@ from email.utils import parsedate as _parsedate
 from threading import RLock
 
 try:
-    ParamSpec = _ty.ParamSpec
+    ParamSpec = _ty.ParamSpec  # 3.10+
 except AttributeError:
     try:
         from typing_extensions import ParamSpec
     except ImportError:
-        ParamSpec = _ty.TypeVar
+
+        class ParamSpec(_ty.TypeVar, _root=True):
+            """Minimal `ParamSpec` stand-in for 3.9 without `typing_extensions`.
+
+            Only the `.args` / `.kwargs` attributes are needed: they appear in
+            annotations that must merely *evaluate*, and a plain `TypeVar` has
+            neither. `typing_extensions` is not a runtime dependency, so the
+            fallback keeps a bare 3.9 install importable.
+            """
+
+            @property
+            def args(self):
+                return self
+
+            @property
+            def kwargs(self):
+                return self
+
 
 K = ParamSpec("K")
 V = _ty.TypeVar("V")

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/tests/test_smoke.py

@@ -4,6 +4,8 @@ These are the snippets from README.md's Quick start and examples/example.py
 that don't touch the network. On Python 3.9 this file is expected to fail
 until the Python 3.9 compatibility work lands.
 """
+import pytest
+
 import pathlib_next
 from pathlib_next import Path, glob
 from pathlib_next.mempath import MemPath
@@ -27,6 +29,7 @@ def test_readme_local_path():
 
 
 def test_readme_http_path_construct_only():
+    pytest.importorskip("requests")
     http_path = UriPath("http://example.com/data.txt")
     assert http_path.source.scheme == "http"
 
@@ -80,6 +83,7 @@ def test_example_uripath_norm():
 
 
 def test_example_uripath_sftp_join():
+    pytest.importorskip("paramiko")
     sftp_root = UriPath("sftp://root@sftpexample/")
     sftp_root.as_posix()
     authkeys = sftp_root / "root/.ssh/authorized_keys"
@@ -111,9 +115,10 @@ def test_optional_schemes_presence_or_absence():
     except ImportError:
         assert not hasattr(schemes, "SftpPath")
 
-    # Check s3
+    # Check s3 -- S3Path only needs botocore at import time (boto3 itself is
+    # a lazy import inside S3Backend.client()), so that's what gates it.
     try:
-        import boto3  # noqa: F401
+        import botocore  # noqa: F401
         assert hasattr(schemes, "S3Path")
     except ImportError:
         assert not hasattr(schemes, "S3Path")

{pathlib_next-0.8.0 → pathlib_next-0.8.1}/tests/test_utils.py

@@ -1,3 +1,8 @@
+import pathlib
+import subprocess
+import sys
+import textwrap
+
 import pytest
 
 from pathlib_next import utils
@@ -306,3 +311,59 @@ def test_detect_format_does_not_peek_when_extension_is_conclusive():
     assert _detect_format("a.tar", _boom) == "tar"
 
 
+
+
+@pytest.mark.skipif(
+    sys.version_info >= (3, 10),
+    reason="the ParamSpec fallback is only reachable on 3.9 (3.10+ has typing.ParamSpec)",
+)
+def test_paramspec_fallback_importable_without_typing_extensions():
+    # Regression: on Python 3.9 `typing.ParamSpec` does not exist, so the module
+    # falls back to `typing_extensions.ParamSpec` and, failing that, to a local
+    # shim. The old fallback was a bare `TypeVar`, which has no `.args`, so the
+    # `*args: K.args` annotations raised `AttributeError: 'TypeVar' object has no
+    # attribute 'args'` at import. It went unnoticed because every dev/CI env had
+    # `typing_extensions` installed transitively -- but it is not a runtime
+    # dependency, so a clean 3.9 install of the package could not import it.
+    #
+    # 3.9-only by nature, not by convenience: `Generic[K, V]` on 3.9 rejects a
+    # plain object ("Parameters to generic types must be types"), so the shim must
+    # subclass `TypeVar` -- and `TypeVar` stopped being subclassable in 3.12. The
+    # branch is unreachable on 3.10+ anyway, since `typing.ParamSpec` exists there.
+    #
+    # Runs in a subprocess with `typing_extensions` blocked so the fallback is
+    # exercised for real rather than mocked.
+    probe = textwrap.dedent(
+        """
+        import builtins
+
+        _real_import = builtins.__import__
+
+        def _blocked(name, *a, **k):
+            if name == "typing_extensions":
+                raise ImportError("emulating an env without typing_extensions")
+            return _real_import(name, *a, **k)
+
+        builtins.__import__ = _blocked
+
+        from pathlib_next.utils import LRU, K
+
+        assert K.args is not None, "ParamSpec fallback lost .args"
+        assert K.kwargs is not None, "ParamSpec fallback lost .kwargs"
+        lru = LRU(lambda x: x * 2, maxsize=4)
+        assert lru(21) == 42
+        assert lru(21) == 42
+        lru.invalidate(21)
+        assert lru(21) == 42
+        print("FALLBACK_OK")
+        """
+    )
+    result = subprocess.run(
+        [sys.executable, "-c", probe],
+        capture_output=True,
+        text=True,
+        cwd=pathlib.Path(utils.__file__).parents[3],
+    )
+    assert "FALLBACK_OK" in result.stdout, (
+        f"fallback import failed:\nstdout={result.stdout}\nstderr={result.stderr}"
+    )