specmod 0.6.0__tar.gz → 0.7.0__tar.gz

{specmod-0.6.0 → specmod-0.7.0}/.github/workflows/build.yml

@@ -18,6 +18,8 @@ jobs:
       # fails every job at "Getting action download info", before a step runs.
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
       - run: uv python install 3.11
 
       - name: Build sdist and wheel

{specmod-0.6.0 → specmod-0.7.0}/.github/workflows/docs.yml

@@ -32,6 +32,8 @@ jobs:
       # fails every job at "Getting action download info", before a step runs.
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
       - run: uv python install 3.11
       - run: uv venv # create a venv to install into
 

{specmod-0.6.0 → specmod-0.7.0}/.github/workflows/release.yml

@@ -90,6 +90,8 @@ jobs:
       # fails every job at "Getting action download info", before a step runs.
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
       - run: uv python install 3.11
       - run: uv build
 

{specmod-0.6.0 → specmod-0.7.0}/.github/workflows/test.yml

@@ -21,6 +21,7 @@ jobs:
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
         with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
           enable-cache: true
       - run: uv python install 3.11
       - run: uv venv
@@ -41,6 +42,7 @@ jobs:
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
         with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
           enable-cache: true
       - run: uv python install 3.11
       - run: uv venv
@@ -65,6 +67,7 @@ jobs:
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
         with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
           enable-cache: true
       - run: uv python install ${{ matrix.python-version }}
       - run: uv venv
@@ -93,6 +96,8 @@ jobs:
       # fails every job at "Getting action download info", before a step runs.
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
+        with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
       - run: uv python install 3.11
       - run: uv venv
       # Exercise the declared minimums. CI otherwise installs the newest of
@@ -117,6 +122,7 @@ jobs:
       # Bump this deliberately; do not "tidy" it to `@v10`.
       - uses: astral-sh/setup-uv@v10.0.1
         with:
+          version: "0.13.7"  # see UV_VERSION in tests/test_release_config.py
           enable-cache: true
       - run: uv python install 3.11
       - run: uv venv

specmod-0.7.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.7.0"
+}

{specmod-0.6.0 → specmod-0.7.0}/CHANGELOG.md

@@ -9,6 +9,27 @@ release could have this problem — every later one has a real predecessor tag
 so leave subsequent headings as generated. release-please only prepends to this
 file, so this edit survives. -->
 
+## [0.7.0](https://github.com/sgjholt/SpecMod/compare/v0.6.0...v0.7.0) (2026-11-08)
+
+
+### ⚠ BREAKING CHANGES
+
+* **datasets:** event directories, waveform files and pick files are named in ISO 8601 basic format (`20190826T073047.000000Z`) instead of extended format (`2019-08-26T07:30:47.000000Z`), and `specmod fetch` writes the new names. Run `specmod migrate-names <dir>` on data fetched before 0.7; `Event.directory()` reads the old names with a DeprecationWarning until 0.8. Code that built a path from `Event.origin` or `SpectrumSet.event` should call `specmod.datasets.path_name` on it. See docs/upgrading.md, From 0.6 to 0.7.
+
+### Features
+
+* **datasets:** name times on disk without colons, and migrate existing data ([52168de](https://github.com/sgjholt/SpecMod/commit/52168dea5cd9ffd8ff16dd9dd70996824c0bbb93))
+
+
+### Code Refactoring
+
+* **config:** narrow the default_factory sentinel instead of suppressing mypy ([961da50](https://github.com/sgjholt/SpecMod/commit/961da50c28aa8ba785879a2b2287c219f64ec216))
+
+
+### Documentation
+
+* **roadmap:** file the default change and the config pin as shipped in v0.6.0 ([92eff1a](https://github.com/sgjholt/SpecMod/commit/92eff1af91dceea5ee65da5a55b460c026cb75de))
+
 ## [0.6.0](https://github.com/sgjholt/SpecMod/compare/v0.5.0...v0.6.0) (2026-09-27)
 
 <!-- One Documentation line below was removed by hand, the third edit in this

{specmod-0.6.0 → specmod-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: specmod
-Version: 0.6.0
+Version: 0.7.0
 Summary: A Python toolbox for processing and modelling seismic spectra
 Project-URL: Homepage, https://github.com/sgjholt/SpecMod
 Project-URL: Repository, https://github.com/sgjholt/SpecMod

{specmod-0.6.0 → specmod-0.7.0}/docs/_builders/specmod_tutorial.py

@@ -91,13 +91,15 @@ from pandas.core.series import Series
 import specmod.preprocess as pre
 import specmod.utils as ut
 from specmod.core.collection import SpectrumPair, SpectrumSet
+from specmod.datasets import path_name
 from specmod.pipeline import spectrum_set_from_streams
 from specmod.staged import StagedFit
 
 # Relative to this notebook, so it runs from wherever it is opened.
 EVENTS = Path("data/events")
 EVENT = "2019-08-26T07:30:47.000000Z" # Event origin time
-DATA: Path = EVENTS / EVENT
+# Named without colons, which Windows does not allow: 20190826T073047.000000Z.
+DATA: Path = EVENTS / path_name(EVENT)
 WAVEFORMS: Path = DATA / "waveforms"
 STATIONS: Path = DATA / "stations" / "*.xml"
 PICKS: Path = DATA / "picks"
@@ -1004,7 +1006,7 @@ it, because journal supplements want one.
 code("""
 from specmod.io import load, save
 
-path: Path = save(path=OUTPUT / spectra.event, spectra=spectra)
+path: Path = save(path=OUTPUT / path_name(spectra.event), spectra=spectra)
 print(f"{path}  ({path.stat().st_size // 1024} KB)")
 
 back: SpectrumSet = load(path)
@@ -1016,8 +1018,8 @@ print(
 
 
 code("""
-FitSpectra.write_flatfile(path=OUTPUT / "flatfiles" / f"{spectra.event}.parquet", fits=fits)
-FitSpectra.write_flatfile(path=OUTPUT / "flatfiles" / f"{spectra.event}.csv", fits=fits)
+FitSpectra.write_flatfile(path=OUTPUT / "flatfiles" / f"{path_name(spectra.event)}.parquet", fits=fits)
+FitSpectra.write_flatfile(path=OUTPUT / "flatfiles" / f"{path_name(spectra.event)}.csv", fits=fits)
 sorted(p.name for p in (OUTPUT / "flatfiles").iterdir())
 """)
 

{specmod-0.6.0 → specmod-0.7.0}/docs/releasing-data.md

@@ -30,6 +30,13 @@ station wildcards against the data centre, cuts each channel to the window
 relative to origin, and writes an `EventDirectory` with a `manifest.json`
 beside it.
 
+The event directory and each waveform file carry the origin in ISO 8601 basic
+format — `20200318T130931.000000Z`, not `2020-03-18T13:09:31.000000Z` — because
+the colons are not legal in a Windows file name, and a source distribution or
+archive containing one is refused by uv 0.13. A fetch made before 0.7 has the
+old names: run `specmod migrate-names build/magna_2020` before archiving it,
+which renames them and updates the manifest to match.
+
 Expect it to take a few minutes — Magna is 88 stations across seven networks.
 
 **Check the manifest before going further.** It records what came back, not

{specmod-0.6.0 → specmod-0.7.0}/docs/roadmap.md

@@ -191,9 +191,7 @@ found by a live fetch rather than by the suite:
   as two independent records of one ground motion. `channel_priorities` and
   `location_priorities` rank them, first match wins per station.
 
-## In progress — not yet released
-
-Merged on `main`, and it will name its version when a release goes out.
+## Shipped in v0.6.0
 
 ### The default is FFT with Konno-Ohmachi smoothing
 
@@ -227,6 +225,22 @@ indistinguishable from a regression. They now carry their own settings in
 `tests/golden/reference.toml`, and a default change leaves every one of them
 untouched.
 
+## In progress — not yet released
+
+Merged on `main`, and it will name its version when a release goes out.
+
+### Names on disk carry no colons
+
+Event directories and the files in them were named by the origin as ObsPy
+prints it, `2019-08-26T07:30:47.000000Z`. Windows does not allow the colons,
+and uv 0.13 refuses to build a source distribution containing them, which
+stopped the release. Names are now ISO 8601 basic format,
+`20190826T073047.000000Z`, from `specmod.datasets.path_name`, and
+`specmod fetch` writes them. `specmod migrate-names` renames data written
+earlier and keeps its manifest verifying; until 0.8, data that has not been
+migrated is still found, with a warning.
+[Upgrading](upgrading.md#from-06-to-07) has the steps.
+
 ## Planned
 
 ### 1.0 — the API stops moving
@@ -268,7 +282,15 @@ Twice in a row makes it worth naming: what keeps moving is not the API, it is
 what the API *does* with a setting that was already there. A deprecation cycle
 does not protect against that, since there is nothing to deprecate; the
 [upgrading guide](upgrading.md) is the only thing that does, and 1.0 will not
-change that. The count stands at zero.
+change that.
+
+**v0.6.0 is not clean either, and is the first to break on purpose.** Its
+default estimator and smoother changed, so every result moves unless a
+configuration pinned both; the change is marked breaking, and
+[Upgrading](upgrading.md#from-05-to-06) says what to pin. One signature moved
+as well: the first argument of `load_config` is positional-only, so
+`load_config(start=path)` is now read as a `[start]` configuration section and
+refused. The count stands at zero.
 
 ## After 1.0
 

{specmod-0.6.0 → specmod-0.7.0}/docs/upgrading.md

@@ -1,10 +1,70 @@
 # Upgrading
 
-Five moves are documented here. Most readers porting code want `0.2` to `0.3`,
+Six moves are documented here. Most readers porting code want `0.2` to `0.3`,
 which renamed ten functions in `specmod.preprocess` and changed what they do
-with the stream they are given. The three moves above it rename nothing: they
-change what a setting does, or which one is the default, so the break is in the
-numbers rather than in the call.
+with the stream they are given. Three of the moves above it rename nothing:
+they change what a setting does, or which one is the default, so the break is
+in the numbers rather than in the call. `0.6` to `0.7` renames files on disk,
+and comes with a command that does it for you.
+
+## From 0.6 to 0.7
+
+**Times in file and directory names no longer contain colons.** An event
+directory and the files inside it were named by the origin as ObsPy prints it,
+`2019-08-26T07:30:47.000000Z`. They are now named in ISO 8601 basic format,
+`20190826T073047.000000Z`, through `specmod.datasets.path_name`. Nothing in any
+file changes, only names; no result moves.
+
+The old names had two problems. Windows does not allow a colon in a file name,
+so the repository could not be checked out there, and uv 0.13 refuses to build
+a source distribution containing one, which stopped the release.
+
+| | Before 0.7 | From 0.7 |
+|---|---|---|
+| Event directory | `events/2019-08-26T07:30:47.000000Z/` | `events/20190826T073047.000000Z/` |
+| Waveform file | `LV.L001..HHE_2019-08-26T07:30:47.000000Z` | `LV.L001..HHE_20190826T073047.000000Z` |
+| Pick file | `picks/2019-08-26T07:30:47.000000Z.picks` | `picks/20190826T073047.000000Z.picks` |
+| `manifest.json` `files` keys | the old paths | the new paths |
+
+**`specmod fetch` writes the new names.** Data you fetched with an earlier
+version keeps the old ones until you migrate it.
+
+**To migrate a directory**, point the command at anything that contains event
+data — one fetch, a tree of them, or a checkout's `tutorial/data/events`:
+
+```bash
+specmod migrate-names build/magna_2020 --dry-run   # list what would change
+specmod migrate-names build/magna_2020
+specmod fetch datasets/magna_2020.toml -o build/magna_2020 --verify
+```
+
+It rewrites every extended-format time in every name under the directory, and
+the `files` keys of any `manifest.json` there, so `fetch --verify` still passes:
+the hashes are of file contents, which the migration does not touch. From
+Python it is `specmod.datasets.migrate_names(root, dry_run=False)`, which
+returns the `(old, new)` pairs. Running it twice is safe; the second run finds
+nothing to do. It refuses, before renaming anything, when a new name is
+already taken, which happens when one event exists in both layouts. Which copy
+to keep is yours to decide.
+
+**Unmigrated data is still read, until 0.8.** `Event.directory()` looks for the
+new name first and falls back to the old one with a `DeprecationWarning` naming
+the command to run. The fallback goes in 0.8, under the usual one-minor
+deprecation.
+
+**Code that built a path from the origin string** has to call `path_name`
+instead:
+
+```python
+from specmod.datasets import path_name
+
+event_dir = out / path_name(event.origin)        # was: out / event.origin
+save(spectra_dir / path_name(spectra.event), s)  # was: spectra_dir / spectra.event
+```
+
+The origin itself is unchanged everywhere it is a time rather than a name:
+`Event.origin`, `datasets/*.toml`, the manifest's `resolved.origin`, and
+`SpectrumSet.event` all keep the extended format.
 
 `0.x` ships breaking changes in minor bumps without a deprecation cycle,
 because shimming an API still being worked out costs more than it protects.
@@ -13,8 +73,8 @@ See [Releasing the software](releasing.md#what-a-version-number-means-while-this
 ## From 0.5 to 0.6
 
 **The default estimator is `fft` and the default smoother is `konno_ohmachi`.**
-They were `multitaper` and `log_bins`. Nothing is renamed and no signature
-moves; **every result changes** unless your configuration already pinned both.
+They were `multitaper` and `log_bins`. Nothing is renamed; **every result
+changes** unless your configuration already pinned both.
 
 The two do different jobs. The estimator sets the spectrum that is fitted.
 The smoother sets the band the fit is confined to — the signal-to-noise ratio
@@ -72,6 +132,11 @@ with config.using("studies/my_study.toml"):
 The local file and the environment are excluded inside the block, and an
 explicit `load_config(project_file=...)` still wins.
 
+**The first argument of `load_config` is positional-only.**
+`load_config(start=path)` now reads `start` as a configuration section and
+raises `ValueError: Configuration section [start] must be a table`; write
+`load_config(path)`. The keyword arguments are unchanged.
+
 ## From 0.4 to 0.5
 
 **`max_radius_km` and `min_radius_km` now mean kilometres.** They were converted

{specmod-0.6.0 → specmod-0.7.0}/src/specmod/acquire.py

@@ -38,7 +38,7 @@ from pathlib import Path
 from typing import Any
 
 from . import __version__
-from .datasets import Event, EventDirectory
+from .datasets import Event, EventDirectory, path_name
 
 __all__ = [
     "AcquisitionConfig",
@@ -567,7 +567,10 @@ def fetch(
     bulk = _bulk_request(inventory, config, start, end)
     stream = client.get_waveforms_bulk(bulk)
 
-    paths = EventDirectory(Path(out) / event.origin)
+    # Named by `path_name`, never by the origin string itself: its colons are
+    # not legal in a Windows name, and a source distribution carrying one is
+    # refused by uv 0.13.
+    paths = EventDirectory(Path(out) / path_name(event.origin))
     paths.waveforms.mkdir(parents=True, exist_ok=True)
     paths.stations.mkdir(parents=True, exist_ok=True)
     paths.picks.mkdir(parents=True, exist_ok=True)
@@ -576,7 +579,7 @@ def fetch(
     for trace in stream:
         # One file per channel, named as the shipped data is, so a fetched
         # event and a committed one are read by the same code.
-        name = f"{trace.id}_{trace.stats.starttime}"
+        name = f"{trace.id}_{path_name(trace.stats.starttime)}"
         target = paths.waveforms / name
         trace.write(str(target), format="MSEED")
         written[str(target.relative_to(Path(out)))] = _sha256(target)

{specmod-0.6.0 → specmod-0.7.0}/src/specmod/cli.py

@@ -19,6 +19,7 @@ from .acquire import fetch, verify
 from .config import load_config
 from .config.provenance import Provenance
 from .config.serialize import to_toml
+from .datasets import migrate_names
 
 #: Shared by every command that resolves configuration, so the layering flags
 #: cannot drift apart between them.
@@ -135,5 +136,27 @@ def fetch_command(config_file: str, out: str, verify_only: bool) -> None:
     )
 
 
+@main.command("migrate-names")
+@click.argument("root", type=click.Path(exists=True, file_okay=False))
+@click.option(
+    "--dry-run",
+    is_flag=True,
+    help="List what would be renamed, and rename nothing.",
+)
+def migrate_names_command(root: str, dry_run: bool) -> None:
+    """Rename event data written before 0.7 to colon-free names.
+
+    Every time in a file or directory name under ROOT is rewritten from
+    2019-08-26T07:30:47.000000Z to 20190826T073047.000000Z, and any
+    manifest.json there is updated to match, so `fetch --verify` still
+    passes. File contents are untouched. Safe to run twice.
+    """
+    renames = migrate_names(root, dry_run=dry_run)
+    for old, new in renames:
+        click.echo(f"{old} -> {new.name}")
+    verb = "would rename" if dry_run else "renamed"
+    click.echo(f"{root}: {verb} {len(renames)} path(s)")
+
+
 if __name__ == "__main__":  # pragma: no cover
     main()

{specmod-0.6.0 → specmod-0.7.0}/src/specmod/config/sections.py

@@ -12,7 +12,7 @@ values used for the published Magna run. Those live in
 
 from __future__ import annotations
 
-from dataclasses import dataclass, field, fields, is_dataclass
+from dataclasses import MISSING, dataclass, field, fields, is_dataclass
 from typing import Any, Literal, Self
 
 __all__ = [
@@ -396,9 +396,14 @@ class Config:
                 f"Valid sections are {sorted(known)}."
             )
         kwargs: dict[str, Any] = {}
-        for name, f in ((f.name, f) for f in fields(cls)):
-            if name in data:
-                kwargs[name] = _build_section(f.default_factory(), data[name], name)  # type: ignore[misc]
+        for f in fields(cls):
+            if f.name in data:
+                # Every section field has a default_factory; the check narrows
+                # the MISSING sentinel away for the type checker.
+                assert f.default_factory is not MISSING
+                kwargs[f.name] = _build_section(
+                    f.default_factory(), data[f.name], f.name
+                )
         return cls(**kwargs)
 
 

{specmod-0.6.0 → specmod-0.7.0}/src/specmod/datasets.py

@@ -4,7 +4,7 @@ The layout follows ObsPy's ``mass_downloader``, which writes ``waveforms/``
 and ``stations/`` beneath a per-event directory. This adds the three things a
 spectral workflow needs alongside them::
 
-    tutorial/data/events/<origin>/
+    tutorial/data/events/<path_name(origin)>/
         event.xml                  # QuakeML: origin, magnitudes, uncertainties
         waveforms/                 # one miniSEED file per channel
         stations/inventory.xml     # StationXML for those channels
@@ -20,6 +20,14 @@ Datasets that ship with the repository have their own loader —
 :func:`load_pnr_2019` — and need no network. Published ones are fetched by
 :func:`load`, cached by pooch and pinned by hash. :mod:`specmod.acquire`
 produces both.
+
+A time in a file or directory name is written by :func:`path_name`, in ISO 8601
+basic format — ``20190826T073047.000000Z`` rather than
+``2019-08-26T07:30:47.000000Z``. The extended form's colons are not legal in a
+Windows file name, and uv 0.13 refuses to build a source distribution that
+contains one. Directories written before 0.7 used the extended form;
+:func:`migrate_names` renames them, and :meth:`Event.directory` still finds an
+unmigrated one until 0.8.
 """
 
 from __future__ import annotations
@@ -27,6 +35,8 @@ from __future__ import annotations
 import glob
 import json
 import os
+import re
+import warnings
 from dataclasses import dataclass
 from pathlib import Path
 from typing import Any
@@ -42,11 +52,45 @@ __all__ = [
     "data_dir",
     "load",
     "load_pnr_2019",
+    "migrate_names",
+    "path_name",
 ]
 
 #: Event directories, relative to the repository root.
 EVENTS = Path("tutorial") / "data" / "events"
 
+#: A time in ISO 8601 extended format, as names were written before 0.7: the
+#: form :func:`str` gives an ``obspy.UTCDateTime``. The colons are what
+#: :func:`migrate_names` exists to remove, so a time without them is left alone.
+_EXTENDED_TIME = re.compile(r"\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d+)?Z?")
+
+
+def path_name(time: Any) -> str:
+    """``time`` as it is written in a file or directory name.
+
+    ISO 8601 basic format with microseconds, ``20190826T073047.000000Z``: no
+    colons, which Windows does not allow in a name and uv 0.13 does not allow
+    in a source distribution, and the same fixed width for every time, so names
+    sort chronologically. Microseconds are kept so that two events in the same
+    second do not share a directory.
+
+    Takes anything ``obspy.UTCDateTime`` accepts, including a name this
+    function produced, so applying it twice changes nothing.
+
+    >>> path_name("2019-08-26T07:30:47.000000Z")
+    '20190826T073047.000000Z'
+    >>> path_name("2019-08-26T07:49:24.2")
+    '20190826T074924.200000Z'
+    """
+    import obspy  # noqa: PLC0415
+
+    return obspy.UTCDateTime(time).strftime("%Y%m%dT%H%M%S.%fZ")
+
+
+def _renamed(name: str) -> str:
+    """``name`` with every extended-format time in it rewritten by :func:`path_name`."""
+    return _EXTENDED_TIME.sub(lambda match: path_name(match.group(0)), name)
+
 
 @dataclass(frozen=True)
 class EventDirectory:
@@ -133,13 +177,32 @@ class Event:
     catalogue_magnitude_type: str | None = None
 
     def directory(self, project_root: Path | str) -> EventDirectory:
-        """Locate this event beneath ``project_root``, the repository root."""
-        return EventDirectory(Path(project_root) / EVENTS / self.origin)
+        """Locate this event beneath ``project_root``, the repository root.
+
+        The directory is named by :func:`path_name`. One written before 0.7,
+        named by the origin itself, is still found when the new name is
+        absent, with a :class:`DeprecationWarning`; that fallback is removed
+        in 0.8. ``specmod migrate-names`` renames it.
+        """
+        events = Path(project_root) / EVENTS
+        current = events / path_name(self.origin)
+        legacy = events / self.origin
+        if not current.exists() and legacy.is_dir():
+            warnings.warn(
+                f"{legacy} is named in the pre-0.7 layout, whose colons are "
+                f"not legal on Windows; it is read for now, and will not be "
+                f"found from 0.8. Run `specmod migrate-names {events}` to "
+                f"rename it to {current.name}.",
+                DeprecationWarning,
+                stacklevel=2,
+            )
+            return EventDirectory(legacy)
+        return EventDirectory(current)
 
 
 #: Preston New Road, 26 August 2019 — the induced event the tutorial and both
 #: golden references are built around, and the largest of the PNR-2 sequence.
-#: The origin time doubles as the directory name.
+#: The origin time, through :func:`path_name`, is the directory name.
 #:
 #: ``Mw 2.9`` is from the PNR-2 catalogue published with Cuadrilla's
 #: hydraulic-fracture monitoring (NGDC, `709cbc2f-af5c-4d09-a4ea-6deb5aa8c5d8
@@ -314,3 +377,78 @@ def load(name: str, *, downloader: Any = None) -> Dataset:
         json.loads(manifest_file.read_text()) if manifest_file.is_file() else None
     )
     return Dataset(event=spec.event, paths=paths, manifest=manifest)
+
+
+# --------------------------------------------------------------- migrating
+
+
+def migrate_names(
+    root: Path | str, *, dry_run: bool = False
+) -> list[tuple[Path, Path]]:
+    """Rename every file and directory under ``root`` to the 0.7 layout.
+
+    Each ISO 8601 extended-format time in a name is rewritten by
+    :func:`path_name`, so ``2019-08-26T07:30:47.000000Z/`` becomes
+    ``20190826T073047.000000Z/`` and a waveform file
+    ``LV.L001..HHE_2019-08-26T07:30:47.000000Z`` becomes
+    ``LV.L001..HHE_20190826T073047.000000Z``. Nothing else in a name changes,
+    and no file's contents change, so every hash a manifest records stays
+    valid. What a ``manifest.json`` under ``root`` changes is its ``files``
+    keys, which are paths: they are rewritten the same way, so
+    ``specmod fetch --verify`` still passes afterwards.
+
+    Returns ``(old, new)`` for every rename, deepest first, which is the order
+    they are made in. With ``dry_run`` nothing is renamed or rewritten. Running
+    it again on a migrated tree finds nothing to do.
+
+    Refuses before renaming anything if a new name is already taken, so a tree
+    that holds both layouts of one event is left for a person to reconcile
+    rather than half-migrated.
+    """
+    root = Path(root)
+    if not root.is_dir():
+        raise NotADirectoryError(f"{root} is not a directory")
+
+    # Deepest first, so a directory is renamed after everything inside it and
+    # no path in the plan is invalidated by an earlier rename.
+    renames: list[tuple[Path, Path]] = []
+    for path in sorted(root.rglob("*"), key=lambda p: len(p.parts), reverse=True):
+        new_name = _renamed(path.name)
+        if new_name != path.name:
+            renames.append((path, path.with_name(new_name)))
+
+    targets = [new for _, new in renames]
+    taken = [new for new in targets if new.exists()]
+    if len(set(targets)) != len(targets) or taken:
+        clash = taken or [t for t in targets if targets.count(t) > 1]
+        raise FileExistsError(
+            f"migrating {root} would overwrite {sorted(set(map(str, clash)))}. "
+            f"Nothing was renamed: this tree holds both layouts of the same "
+            f"data, and which copy to keep is not a choice to make silently."
+        )
+
+    # Where each manifest will be once its directories are renamed.
+    manifests = [
+        root.joinpath(*(_renamed(part) for part in path.relative_to(root).parts))
+        for path in root.rglob("manifest.json")
+        if path.is_file()
+    ]
+    if dry_run:
+        return renames
+
+    for old, new in renames:
+        old.rename(new)
+
+    for manifest_file in manifests:
+        manifest = json.loads(manifest_file.read_text())
+        files = manifest.get("files")
+        if not isinstance(files, dict):
+            continue
+        migrated = {
+            "/".join(_renamed(part) for part in name.split("/")): digest
+            for name, digest in files.items()
+        }
+        if migrated != files:
+            manifest["files"] = dict(sorted(migrated.items()))
+            manifest_file.write_text(json.dumps(manifest, indent=1) + "\n")
+    return renames

{specmod-0.6.0 → specmod-0.7.0}/stubs/obspy/core/utcdatetime.pyi

@@ -41,3 +41,4 @@ class UTCDateTime:
     def second(self) -> int: ...
     @property
     def microsecond(self) -> int: ...
+    def strftime(self, format: str) -> str: ...