pyflightstream 0.40.0__tar.gz → 0.41.0__tar.gz

{pyflightstream-0.40.0/src/pyflightstream.egg-info → pyflightstream-0.41.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pyflightstream
-Version: 0.40.0
+Version: 0.41.0
 Summary: Version-aware, didactic Python driver for the FlightStream panel-method solver
 Author: Geovana Neves
 License: MIT
@@ -60,7 +60,10 @@ Version-aware Python driver for the FlightStream panel-method solver: write a
 run matrix, and pyflightstream plans, runs and post-processes every point,
 from your workstation or a cluster. MIT licensed.
 
-Status: v0.40.0 is the current release; CHANGELOG.md carries the history.
+This source tree contains 0.41.0; CHANGELOG.md describes its changes and the
+retained release history.
+Use the [upgrade guidance](https://nevesgeovana.github.io/pyflightstream/upgrading/)
+when moving an existing workspace to a newer package version.
 
 **Documentation: [nevesgeovana.github.io/pyflightstream](https://nevesgeovana.github.io/pyflightstream/)**
 
@@ -94,18 +97,19 @@ pip install "pyflightstream[geom,fsi,plot,excel]"
 Python 3.12 or newer. FlightStream itself is licensed separately and is
 located through your workspace, never guessed.
 
-## Quick start
+## Quick start without a solver
 
 ```
-pyfs-workspace init my-study            # the workspace tree and input folders
-cd my-study                             # add a geometry, a matrix, a reference, a setup
-pyfs-matrix plan matriz.fs              # zero solver time: what will run, what is refused
-pyfs-matrix run matriz.fs               # runs every READY point
-pyfs-matrix post --workspace .          # rebuilds the products from the records
+pyfs-workspace init my-study
 ```
 
 [Getting started](https://nevesgeovana.github.io/pyflightstream/getting-started/)
-walks a first workspace file by file, and
+starts with an executable solver-free example, then walks the geometry,
+matrix, reference, setup and post-processing inputs needed before planning.
+Initialization creates `my-study/inputs/INPUTS.md`; read it next. Planning
+needs those inputs but no solver license. Running requires a separately
+licensed FlightStream installation.
+
 [From the GUI to pyfs](https://nevesgeovana.github.io/pyflightstream/gui-to-pyfs/)
 maps each GUI step to the key that takes it here.
 
@@ -113,7 +117,7 @@ maps each GUI step to the key that takes it here.
 
 | Tool | What it is for |
 |---|---|
-| `pyfs-workspace` | Create a workspace; archive a simulation; reorganise the geometry library |
+| `pyfs-workspace` | Create or migrate a workspace; archive simulations; prepare geometry, custom fields and actuator profiles |
 | `pyfs-matrix` | Plan, run, collect and post a run matrix; storage (`space-in-use`, `free-space`, `delete-sims`) and `sync` between workspaces |
 | `pyfs-qa` | Command-validity probes and physics regression on a licensed machine |
 | `pyfs-fsi` | The structural executable of the aeroelastic coupling loop |
@@ -127,7 +131,7 @@ maps each GUI step to the key that takes it here.
 | Parsers, tables, run manifest, reconstruction | supported |
 | Campaigns, run matrices, workspace, pre-flight | supported |
 | Far-field ledgers and probe surveys | **experimental** |
-| FSI structural beam and modal analysis | **experimental** (`examples/wing_static_deflection.py`, `examples/fsi_campbell_diagram.py`) |
+| FSI structural beam and modal analysis | **experimental** (`docs/examples/_sources/wing_static_deflection.py`, `docs/examples/_sources/fsi_campbell_diagram.py`) |
 | FSI coupled driver (the four-phase loop) | **experimental**: offline replay only, never run against a live solver in CI |
 | Rotary two-way coupling | **not validated** |
 
@@ -151,8 +155,9 @@ and the evidence behind it is narrower than for the supported rows.
 | 26.125 | 26.12 | `operational` |
 
 `operational` means the minimal geometry-to-loads workflow builds for that
-version, checked by a test; `documented` means the manual has been read but
-nothing has been measured on the build yet. The details, and how to tell
+version, checked by a test. `documented` describes the database support level;
+it does not imply that no measurements exist for that build. Individual commands
+may carry different evidence. The details, and how to tell
 which build you have, are on
 [Which build do I have](https://nevesgeovana.github.io/pyflightstream/builds/):
 

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/README.md

@@ -8,7 +8,10 @@ Version-aware Python driver for the FlightStream panel-method solver: write a
 run matrix, and pyflightstream plans, runs and post-processes every point,
 from your workstation or a cluster. MIT licensed.
 
-Status: v0.40.0 is the current release; CHANGELOG.md carries the history.
+This source tree contains 0.41.0; CHANGELOG.md describes its changes and the
+retained release history.
+Use the [upgrade guidance](https://nevesgeovana.github.io/pyflightstream/upgrading/)
+when moving an existing workspace to a newer package version.
 
 **Documentation: [nevesgeovana.github.io/pyflightstream](https://nevesgeovana.github.io/pyflightstream/)**
 
@@ -42,18 +45,19 @@ pip install "pyflightstream[geom,fsi,plot,excel]"
 Python 3.12 or newer. FlightStream itself is licensed separately and is
 located through your workspace, never guessed.
 
-## Quick start
+## Quick start without a solver
 
 ```
-pyfs-workspace init my-study            # the workspace tree and input folders
-cd my-study                             # add a geometry, a matrix, a reference, a setup
-pyfs-matrix plan matriz.fs              # zero solver time: what will run, what is refused
-pyfs-matrix run matriz.fs               # runs every READY point
-pyfs-matrix post --workspace .          # rebuilds the products from the records
+pyfs-workspace init my-study
 ```
 
 [Getting started](https://nevesgeovana.github.io/pyflightstream/getting-started/)
-walks a first workspace file by file, and
+starts with an executable solver-free example, then walks the geometry,
+matrix, reference, setup and post-processing inputs needed before planning.
+Initialization creates `my-study/inputs/INPUTS.md`; read it next. Planning
+needs those inputs but no solver license. Running requires a separately
+licensed FlightStream installation.
+
 [From the GUI to pyfs](https://nevesgeovana.github.io/pyflightstream/gui-to-pyfs/)
 maps each GUI step to the key that takes it here.
 
@@ -61,7 +65,7 @@ maps each GUI step to the key that takes it here.
 
 | Tool | What it is for |
 |---|---|
-| `pyfs-workspace` | Create a workspace; archive a simulation; reorganise the geometry library |
+| `pyfs-workspace` | Create or migrate a workspace; archive simulations; prepare geometry, custom fields and actuator profiles |
 | `pyfs-matrix` | Plan, run, collect and post a run matrix; storage (`space-in-use`, `free-space`, `delete-sims`) and `sync` between workspaces |
 | `pyfs-qa` | Command-validity probes and physics regression on a licensed machine |
 | `pyfs-fsi` | The structural executable of the aeroelastic coupling loop |
@@ -75,7 +79,7 @@ maps each GUI step to the key that takes it here.
 | Parsers, tables, run manifest, reconstruction | supported |
 | Campaigns, run matrices, workspace, pre-flight | supported |
 | Far-field ledgers and probe surveys | **experimental** |
-| FSI structural beam and modal analysis | **experimental** (`examples/wing_static_deflection.py`, `examples/fsi_campbell_diagram.py`) |
+| FSI structural beam and modal analysis | **experimental** (`docs/examples/_sources/wing_static_deflection.py`, `docs/examples/_sources/fsi_campbell_diagram.py`) |
 | FSI coupled driver (the four-phase loop) | **experimental**: offline replay only, never run against a live solver in CI |
 | Rotary two-way coupling | **not validated** |
 
@@ -99,8 +103,9 @@ and the evidence behind it is narrower than for the supported rows.
 | 26.125 | 26.12 | `operational` |
 
 `operational` means the minimal geometry-to-loads workflow builds for that
-version, checked by a test; `documented` means the manual has been read but
-nothing has been measured on the build yet. The details, and how to tell
+version, checked by a test. `documented` describes the database support level;
+it does not imply that no measurements exist for that build. Individual commands
+may carry different evidence. The details, and how to tell
 which build you have, are on
 [Which build do I have](https://nevesgeovana.github.io/pyflightstream/builds/):
 

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pyflightstream"
-version = "0.40.0"
+version = "0.41.0"
 description = "Version-aware, didactic Python driver for the FlightStream panel-method solver"
 readme = "README.md"
 license = {text = "MIT"}
@@ -187,6 +187,16 @@ testpaths = ["tests"]
 # with `-o pythonpath=`.
 pythonpath = ["src"]
 markers = [
+    "pkg_core: tier-1 core package",
+    "pkg_script_results: tier-1 script-results package",
+    "pkg_probes_farfield: tier-1 probes-farfield package",
+    "pkg_fsi: tier-1 fsi package",
+    "pkg_cases: tier-1 cases package",
+    "pkg_workspace: tier-1 workspace package",
+    "pkg_run: tier-1 run package",
+    "pkg_post: tier-1 post package",
+    "pkg_qa: tier-1 qa package",
+    "pkg_guards: tier-1 repository guards package",
     "needs_flightstream: requires a local FlightStream installation and license",
     "validity: tier 2 per-command probe tests",
     "physics: tier 3 physics regression matrix (slow)",
@@ -276,7 +286,7 @@ exclude_also = [
 # modules exempted below still reports at least one error (re-counted with the
 # sentence above). The per-module figures, the
 # reproduction command and the dependency versions the count rests on are in
-# reports/RPT-029, and `scripts/mypy_recount.py` re-derives every one of them
+# the internal type-debt record; the release tooling re-derives the counts
 # from a single run.
 #
 # THE PROSE AROUND THE SENTENCE IS NOT GUARDED AND WENT STALE ON 2026-08-20,

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_cli.py

@@ -37,7 +37,7 @@ _POST_WARNINGS: ContextVar[bool | None] = ContextVar(
     "pyflightstream_cli_post_warnings", default=None
 )
 #: Python's own warning format, held for the length of one invocation so a
-#: console level chosen after the parse can put it back (FR-436 R6).
+#: console level chosen after the parse can put it back (FR-997).
 _STANDARD_FORMAT: ContextVar[Callable[..., str] | None] = ContextVar(
     "pyflightstream_cli_standard_format", default=None
 )
@@ -73,7 +73,7 @@ def note_post_ran() -> None:
 
 
 def set_post_warning_policy(enabled: bool) -> None:
-    """Set whether this invocation prints grouped post-processing warnings (FR-436 R5).
+    """Set whether this invocation prints grouped post-processing warnings (FR-996).
 
     Read from the raw command line before the parse; a workspace settings file
     or ``--no-pproc-warnings`` decides after it. Outside a console command it
@@ -89,7 +89,7 @@ def set_post_warning_policy(enabled: bool) -> None:
 
 
 def set_console_level(level: str) -> None:
-    """Set the console level of this invocation, chosen after the parse (FR-436 R6).
+    """Set the console level of this invocation, chosen after the parse (FR-997).
 
     ``verbose`` prints warnings in Python's full format, the other two levels in
     the package's short one; :func:`pyflightstream._progress.set_console_level`
@@ -264,7 +264,7 @@ def cli_entrypoint[**P, R](function: Callable[P, R]) -> Callable[P, R]:
             _POSTED.reset(posted_token)
             _POST_WARNINGS.reset(warning_token)
             _ACTIVE.reset(token)
-            # FR-436 R6: a quiet console says its errors and final line, then the signature.
+            # FR-997: a quiet console says its errors and final line, then the signature.
             _progress.release_quiet(terminal, failed=outcome in ("failed", "cancelled"))
             if outcome == "success" and posted[0]:
                 outcome = "post"

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_console.py

@@ -36,7 +36,7 @@ _Subparsers = argparse._SubParsersAction
 #: word longer than the room left (a long path) is kept whole on its own line.
 WIDTH = 90
 
-#: The console levels of a command (FR-436 R6), least to most: ``quiet`` says the
+#: The console levels of a command (FR-997), least to most: ``quiet`` says the
 #: errors, the final summary line and the signature; ``normal`` is the console of
 #: 0.38.0; ``verbose`` is its ``--verbose``. The activity log is full at every level.
 CONSOLE_LEVELS = ("quiet", "normal", "verbose")

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_deprecations.py

@@ -640,100 +640,18 @@ def removed_names_hook(module: str) -> Callable[[str], object]:
     return refuse
 
 
-#: THE VOCABULARY THAT MOVED TO THE REFERENCE (FR-59 and FR-72, the design
-#: of 2026-09-10). Both tables were the setup preset's at 0.14.0, are read
-#: from it with a warning at 0.15.0, and stop being read at 0.17.0. Two
-#: releases rather than one because a workspace migrates its inputs by
-#: hand and the tables are shared by every row of a configuration.
-_MOVED_TO_THE_REFERENCE = (
-    "A boundary name and a coordinate system are properties of the "
-    "CONFIGURATION, and a preset is per condition."
-)
-SETUP_ALIASES_TABLE = DeprecatedParameter(
-    owner="the setup preset",
-    old="[aliases]",
-    new="the same table in the reference artifact",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=_MOVED_TO_THE_REFERENCE,
-)
-SETUP_FRAMES_TABLE = DeprecatedParameter(
-    owner="the setup preset",
-    old="[[frames]]",
-    new="the same table in the reference artifact",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=_MOVED_TO_THE_REFERENCE,
-)
-#: THE FIVE ROW KEYS AN ALIAS REPLACES (FR-61). The reference states each
-#: of them once, in the rotor's own block, so a row states the alias and
-#: nothing else about the rotor.
-_STATED_IN_THE_BLOCK = (
-    "The reference states it once, in the rotor's own block, and a row names the rotor by alias."
-)
+#: A motion record must name its rotor by alias. Flat rotor rows retain their
+#: accepted axis, origin, sign and blade-count keys; this refusal is conditional
+#: on MOVING_BOUNDARIES appearing inside a MOTIONS record.
 ROW_MOVING_BOUNDARIES = DeprecatedParameter(
-    owner="a motion record",
+    owner="a MOTIONS record",
     old="MOVING_BOUNDARIES",
     new="MOVING_BC_ALIAS",
     deprecated_since="0.15.0",
     removal_version="0.18.0",
-    extra=_STATED_IN_THE_BLOCK,
-)
-ROW_ROTOR_AXIS = DeprecatedParameter(
-    owner="a motion record",
-    old="ROTOR_AXIS",
-    new="the axis of the rotor the record names",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=_STATED_IN_THE_BLOCK,
-)
-ROW_ROTOR_ORIGIN = DeprecatedParameter(
-    owner="a motion record",
-    old="ROTOR_ORIGIN",
-    new="the hub of the rotor the record names",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=_STATED_IN_THE_BLOCK,
-)
-ROW_RPM_SIGN = DeprecatedParameter(
-    owner="a motion record",
-    old="RPM_SIGN",
-    new="the rpm_sign of the rotor the record names",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=_STATED_IN_THE_BLOCK,
-)
-ROW_BLADES = DeprecatedParameter(
-    owner="a motion record",
-    old="BLADES",
-    new="the length of that rotor's families_blades",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
     extra=(
-        "The reference states the blade FAMILIES and the count is how many "
-        "there are, so a sector mesh carrying one blade of four still "
-        "reduces over four and no row states a number that can disagree "
-        "with the file it opens."
-    ),
-)
-#: A KEY BECOMING REQUIRED IS NOT A RENAME, and this is the first entry of
-#: that shape. `old` is the ABSENCE and `new` is the key, because what a
-#: reader needs is the sentence "you have until 0.17.0 to add this", which
-#: the ledger's own renderer produces from those two fields. Written here
-#: rather than only in the warning string, because a promise the deadline
-#: guard cannot see is a promise nothing keeps (the interface lens of the
-#: 0.15.0 release review).
-ROW_CLOCK_MOTION_ON_A_FLAT_ROW = DeprecatedParameter(
-    owner="a rotor row in the pre-0.15.0 spelling",
-    old="no CLOCK_MOTION, the clock following the fastest rotor",
-    new="CLOCK_MOTION naming the motion that owns the clock",
-    deprecated_since="0.15.0",
-    removal_version="0.18.0",
-    extra=(
-        "A row stating a MOTIONS list is refused without the key since "
-        "0.15.0. A flat-form row that turns more than one rotor is refused "
-        "without it as well, and a flat-form row turning ONE rotor needs no "
-        "key, because there is nothing to choose between."
+        "A MOTIONS record names a rotor alias from the reference. "
+        "Flat rotor row keys remain accepted."
     ),
 )
 ROW_ROTATE_FAMILIES = DeprecatedParameter(
@@ -795,30 +713,11 @@ ROW_BLADES_SELECTOR = DeprecatedParameter(
 #: the entry moves rather than staying here unspoken. Its home is
 #: :data:`pyflightstream._retired_names.PROBE_SCALE_PROPELLER_RADIUS`.
 
-#: THE 0.15.0 BATCH, WHICH IS NOT A SET OF PROMISES. Every entry below was
-#: written in 0.15.0 and 0.15.0 has not shipped, so nobody has a workspace
-#: that was told the old spelling would keep working. The decision of
-#: 2026-09-10 is that this release breaks them rather than carrying two
-#: vocabularies into a package with no stable version: a promise made
-#: inside an unreleased version was never a promise to anyone.
-#:
-#: The entries stay as objects because their `message()` is the sentence the
-#: REFUSALS print, and one home for a sentence is what this module is for.
-#: They are out of :data:`DEPRECATIONS` because that tuple is what the Tier 1
-#: deadline guard reads, and there is no shim left for it to watch expire.
-#:
-#: The 0.14.0 batch is deliberately NOT here. Those promises were published,
-#: they expire at 0.16.0 which is the next release anyway, and breaking them
-#: would break a workspace that upgraded on the strength of them.
+#: Live refusal messages for removed spellings, not unconditional bans on
+#: flat rotor row keys. These entries have callers; obsolete catalog-only
+#: entries are not promises or active refusals.
 REFUSED_IN_0_15_0: tuple[Deprecation, ...] = (
-    SETUP_ALIASES_TABLE,
-    SETUP_FRAMES_TABLE,
     ROW_MOVING_BOUNDARIES,
-    ROW_ROTOR_AXIS,
-    ROW_ROTOR_ORIGIN,
-    ROW_RPM_SIGN,
-    ROW_BLADES,
-    ROW_CLOCK_MOTION_ON_A_FLAT_ROW,
     ROW_ROTATE_FAMILIES,
     ROW_EACH_BLADE,
     ROW_AIRFRAME_SELECTOR,

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_digest.py

@@ -124,6 +124,11 @@ EXCLUDED_FROM_EVERY_DIGEST = (
 #: package for every ``hashlib`` call and fails on a module absent here,
 #: so a new digest cannot enter with its canonical form unstated.
 CANONICAL_FORMS = {
+    "workspace/record_document.py": (
+        "the UTF-8 encoding of JSON with sorted keys, compact comma/colon separators "
+        "and ensure_ascii=True for each shared solver, frame or geometry definition. "
+        "The full SHA-256 names the immutable definition in its workspace registry."
+    ),
     "_digest.py": (
         "the raw bytes of a file, read in blocks and never decoded; or the "
         "UTF-8 encoding of a string. Nothing else is read: not the path, not "
@@ -225,7 +230,7 @@ CANONICAL_FORMS = {
         "newline, 'name key=value ...' with the keys sorted, factor always "
         "written and every other option only when it is not its default, a "
         "number as the shortest text that reads back to the same float without "
-        "a trailing '.0' (FR-433 R2). The first 8 hexadecimal characters name a "
+        "a trailing '.0' (FR-970). The first 8 hexadecimal characters name a "
         "level folder whose automatic tag is too long; refine.json lists the "
         "selected families as tag_selection, not the text."
     ),

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_errors.py

@@ -171,15 +171,8 @@ class ProductArgumentError(PyflightstreamError, TypeError):
 class ProductError(PyflightstreamError, ValueError):
     """A product cannot be written from what the run left.
 
-    DEFINED HERE RATHER THAN IN :mod:`pyflightstream.post._tables` since
-    0.23.0, and for the reason `InputArtifactError` is: TWO LAYERS NAME IT.
-    The post layer raises it, and `workspace.rename_groups` -- the migration
-    that moves a user's existing products -- raised it by importing UPWARD into
-    `post`, an edge on the package's own import path that resolved only by the
-    relative order of two lines in a third file. Moving that block, or adding
-    any earlier `workspace` import to `post.products`, stopped the package
-    importing at all. An architecture lens found it; a circular import while
-    wiring item 14 is what made it urgent.
+    Defined in the shared error catalogue so callers can catch a product
+    refusal without importing the post-processing layer.
 
     `post.products` re-exports it, so the public name and the pair of bases are
     unchanged and `except ValueError` catches exactly what it always did.

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_fsm.py

@@ -1010,7 +1010,7 @@ def surface_mesh(
 def boundary_owners(path: str | Path) -> tuple[int, ...]:
     """Return the boundary of every face of a saved simulation's mesh block, counted from 1.
 
-    The geometry stage colours its preview by it (FR-471 R6). Empty where the
+    The geometry stage colours its preview by it (FR-1107). Empty where the
     block carries no boundary row this reader recognises.
 
     Raises

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_fsm_fresh.py

@@ -11,7 +11,7 @@ trailing edges and the others), and everything else should come from the
 script. So every block other than those is put back to the content a freshly
 imported file holds.
 
-WHAT IS RESET IS MEASURED, NEVER GUESSED (FR-312 R2). A saved simulation is a
+WHAT IS RESET IS MEASURED, NEVER GUESSED (FR-531). A saved simulation is a
 sequence of ``$<NAME>_START$`` ... ``$<NAME>_END$`` blocks after a two-line
 head (the solver's version, then its build). Measured on 2026-09-30 over the
 ten committed tier-3 geometries, which the tier-3 preparation made by
@@ -375,7 +375,7 @@ def reset_to_fresh_import(text: str, unit: str | None, where: str) -> FreshReset
             (),
             f"{where}: no fresh import of build {build or 'unknown'} saved in "
             f"{unit or 'an unread unit'} is measured, so every block other than the "
-            "saved solver actions is kept as it is (FR-312 R2)",
+            "saved solver actions is kept as it is (FR-531)",
         )
     eol, lines = _lines(text)
     held = block_lines(text)

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_maturity.py

@@ -248,8 +248,6 @@ MATURITY = {
     "pyflightstream.run.matrix": "stable",
     # Module path added after v0.30.0.
     "pyflightstream.run.records": "provisional",
-    # v0.30.0: run/rename.py
-    "pyflightstream.run.rename": "stable",
     # v0.30.0: script/__init__.py
     "pyflightstream.script": "stable",
     # v0.30.0: script/entities.py
@@ -316,10 +314,12 @@ MATURITY = {
     "pyflightstream.workspace.manifest": "provisional",
     # v0.30.0: workspace/matrix.py
     "pyflightstream.workspace.matrix": "stable",
+    # 0.41.0: explicit workspace migration and shared record definitions.
+    "pyflightstream.workspace.migrate": "provisional",
     # v0.30.0: workspace/naming.py
     "pyflightstream.workspace.naming": "stable",
-    # v0.30.0: workspace/rename_groups.py
-    "pyflightstream.workspace.rename_groups": "stable",
+    # 0.41.0: shared record definitions.
+    "pyflightstream.workspace.record_document": "provisional",
     # Module path added after v0.30.0.
     "pyflightstream.workspace.selections": "provisional",
     # v0.30.0: workspace/setup_inspection.py

{pyflightstream-0.40.0 → pyflightstream-0.41.0}/src/pyflightstream/_progress.py

@@ -133,7 +133,7 @@ class _Terminal:
         self.console: _Console | None = None
         #: The width of the progress line a terminal shows now, to clear before any other line.
         self.redrawn = 0
-        #: The ``quiet`` console level (FR-436 R6): what the console would show is
+        #: The ``quiet`` console level (FR-997): what the console would show is
         #: held, and only the errors and the final summary line are said at the end.
         self.quiet = False
         #: How deep the console is in its own chatter (the opening block, a stage
@@ -173,7 +173,7 @@ def command_terminal(*, verbose: bool) -> Iterator[_Terminal]:
 
 
 def set_console_level(level: str) -> None:
-    """Set the console level of the running command (FR-436 R6).
+    """Set the console level of the running command (FR-997).
 
     ``verbose`` is the console of ``--verbose``; ``normal`` the default one;
     ``quiet`` holds everything the console would show and, once the command
@@ -220,7 +220,7 @@ def _chatter() -> Iterator[None]:
 
 
 def quiet_keeps(text: str, *, error: bool = False) -> None:
-    """State a command's final summary, or one of its errors, for a quiet console (FR-436 R6).
+    """State a command's final summary, or one of its errors, for a quiet console (FR-997).
 
     A ``quiet`` console says, once the command has ended, the errors and the
     final summary line a command states here, whatever stream the command
@@ -250,7 +250,7 @@ def say_summary(text: str) -> None:
     """Print a command's final summary line on standard output, stated for a quiet console.
 
     The same line :func:`print` writes, at every level; a ``quiet`` console
-    says it once the command has ended (FR-436 R6, :func:`quiet_keeps`).
+    says it once the command has ended (FR-997, :func:`quiet_keeps`).
 
     Parameters
     ----------
@@ -788,7 +788,7 @@ class _ConsoleStream:
     Each write clears a progress line a terminal shows, says the opening block
     first where it is still owed, then goes to the stream it wraps and to the
     live log. Every other attribute is the wrapped stream's. On a ``quiet``
-    console (FR-436 R6) a write still reaches the live log and is not said:
+    console (FR-997) a write still reaches the live log and is not said:
     of standard error what is not the console's own chatter is held, for
     :func:`release_quiet` to say if the command fails; standard output is
     said only through what the command states with :func:`quiet_keeps`.