[pytooling-claude]

Note

A patch release on @r9 without new inputs: ComputePacboyPackages follows pyTooling v10's extras (dependencies, idna, tracing) and drops the sphinx-reports rule, the multi-line if: conditions of CompletePipeline.yml are written without ${{ }}, the job template check of PublishOnPyPI publishes no source distribution, and the documentation names the analyzer behind its coverage page.

🔧 Changes

• ComputePacboyPackages, the pip → MSYS2 package table (ComputePacboyPackages: pyTooling's extras 'dependencies' and 'idna', no sphinx_reports rule #328):
  • pyTooling v10 renames its extra pypi to dependencies (Extra 'pypi' is named 'dependencies' pyTooling#635): pyTooling[dependencies] maps to python-aiohttp:p, like pyTooling[pypi], whose rule stays for pyTooling up to v10.0.0-rc8 (ComputePacboyPackages: keep the rule for pyTooling's extra 'pypi' #329).
  • pyTooling's new extras idna and tracing map to python-idna:p and python-jsonschema:p, the requirement idna to python-idna:p.
  • The rule for sphinx_reports is removed: pyTooling.Sphinx replaced sphinx-reports. The rule for pyedaa.osvvm lists python-jsonschema:p, which pyEDAA.OSVVM needs through pyEDAA.Reports, instead of sphinx-reports' packages.

📖 Documentation

• doc/DocCoverage.rst: the documentation coverage is analyzed by pyEDAA.Reports.DocumentationCoverage.Python.Analyzer and visualized by pyTooling.Sphinx. The page named docstr-coverage, which the report:doc-coverage directive doesn't use. The CheckDocumentation job template, which runs the docstr-coverage CLI, is unchanged (Documentation coverage page names pyEDAA.Reports' analyzer #325).

🧪 Unit Tests

• _Checking_JobTemplates.yml: the PublishOnPyPI dry run sets publish_sdist: 'false', as pyTooling's own pipeline does. The dry run checks the wheel with twine check and skips the step checking the source package (Checking: the PublishOnPyPI dry run publishes no source distribution #321).

⚙️ GitHub Pipeline

• Pipeline.yml: the multi-line condition of the References job is written without ${{ }} (Multi-line 'if:' conditions without '${{ }}' #324).

Others

• CompletePipeline.yml: the 7 multi-line if: conditions - both artifact clean-ups, the PDF documentation, the GitHub Pages publication, tagging, the release page and the PyPI publication - are written without ${{ }}. An if: is an expression anyway; each condition's text equals the old one without ${{ and }}, so the jobs run under the same conditions as before. Single-line conditions are untouched (Multi-line 'if:' conditions without '${{ }}' #324).
• doc/conf.py, tests/pacman_packages.py and tests/python_jobs.py: 9 f-strings without placeholder are plain strings; every string keeps its value (f-strings without placeholder are plain strings #323).
• Version 9.3.1 in myPackage/__init__.py and myFramework/Extension/__init__.py.

---

Related Issues and Pull-Requests

• Checking: the PublishOnPyPI dry run publishes no source distribution #321: the PublishOnPyPI dry run publishes no source distribution (follow-up of Package/PublishOnPyPI: choose source distribution and wheel separately #319).
• f-strings without placeholder are plain strings #323: f-strings without placeholder are plain strings.
• Multi-line 'if:' conditions without '${{ }}' #324: multi-line if: conditions without ${{ }}.
• Documentation coverage page names pyEDAA.Reports' analyzer #325: the documentation coverage page names pyEDAA.Reports' analyzer.
• ComputePacboyPackages: pyTooling's extras 'dependencies' and 'idna', no sphinx_reports rule #328: ComputePacboyPackages follows pyTooling v10's extras; no sphinx-reports rule.
• ComputePacboyPackages: keep the rule for pyTooling's extra 'pypi' #329: the rule for pyTooling's extra pypi stays beside dependencies.
• Previous release: v9.3.0 (v9.3.0 #320).
• Still open, not part of this release: Check a tag against the main branch once instead of three times #254 (tag check once), 'pyedaa.reports' needs no ruamel.yaml packages on MSYS2 #326 (draft, pyedaa.reports without ruamel.yaml packages on MSYS2).

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}