ezmsg-tools 0.1.0__tar.gz

ezmsg_tools-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,66 @@
+name: Documentation
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+      - dev
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Needed for hatch-vcs to determine version
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+          python-version: "3.12"
+
+      - name: Install the project
+        run: uv sync --only-group docs
+
+      - name: Build documentation
+        run: |
+          cd docs
+          uv run make html
+
+      - name: Add .nojekyll file
+        run: touch docs/build/html/.nojekyll
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: 'docs/build/html'
+
+  deploy:
+    # Only deploy when a release is published
+    if: github.event_name == 'release'
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

ezmsg_tools-0.1.0/.github/workflows/python-publish.yml

@@ -0,0 +1,26 @@
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: build and upload release to PyPI
+    runs-on: ubuntu-latest
+    environment: "release"
+    permissions:
+      id-token: write  # IMPORTANT: this permission is mandatory for trusted publishing
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install the latest version of uv
+        uses: astral-sh/setup-uv@v6
+
+      - name: Build Package
+        run: uv build
+
+      - name: Publish package distributions to PyPI
+        run: uv publish

ezmsg_tools-0.1.0/.github/workflows/python-tests.yml

@@ -0,0 +1,36 @@
+name: Test package
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches:
+      - main
+      - dev
+  workflow_dispatch:
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        python-version: ["3.10.15", "3.11", "3.12", "3.13"]
+        os:
+          - "ubuntu-latest"
+          - "windows-latest"
+          - "macos-latest"
+    runs-on: ${{matrix.os}}
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install the latest version of uv
+        uses: astral-sh/setup-uv@v6
+
+      - name: Install the project
+        run: uv sync --python ${{ matrix.python-version }}
+
+      - name: Lint
+        run: uv tool run ruff check --output-format=github src
+
+      - name: Run tests
+        run: uv run pytest tests

ezmsg_tools-0.1.0/.gitignore

@@ -0,0 +1,55 @@
+# These are some examples of commonly ignored file patterns.
+# You should customize this list as applicable to your project.
+# Learn more about .gitignore:
+#     https://www.atlassian.com/git/tutorials/saving-changes/gitignore
+
+# Node artifact files
+node_modules/
+dist/
+
+# Compiled Java class files
+*.class
+
+# Compiled Python bytecode
+*.py[cod]
+
+# Log files
+*.log
+
+# Package files
+*.jar
+
+# Maven
+target/
+dist/
+
+# JetBrains IDE
+.idea/
+
+# Unit test reports
+TEST*.xml
+
+# Generated by MacOS
+.DS_Store
+
+# Generated by Windows
+Thumbs.db
+
+# Applications
+*.app
+*.exe
+*.war
+
+# Large media files
+*.mp4
+*.tiff
+*.avi
+*.flv
+*.mov
+*.wmv
+
+.venv/
+src/ezmsg/tools/__version__.py
+
+uv.lock
+settings.local.json

ezmsg_tools-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,9 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.8.3
+    hooks:
+      # Run the linter.
+      - id: ruff
+        args: [ --fix ]
+      # Run the formatter.
+      - id: ruff-format

ezmsg_tools-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 ezmsg-org
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ezmsg_tools-0.1.0/PKG-INFO

@@ -0,0 +1,115 @@
+Metadata-Version: 2.4
+Name: ezmsg-tools
+Version: 0.1.0
+Summary: ezmsg namespace package containing tools for working with ezmsg graphs.
+Author-email: Chadwick Boulay <chadwick.boulay@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10.15
+Requires-Dist: ezmsg>=3.6.1
+Requires-Dist: numpy>=1.26.0
+Provides-Extra: perfmon
+Requires-Dist: dash-bootstrap-components>=1.6.0; extra == 'perfmon'
+Requires-Dist: dash-extensions>=1.0.19; extra == 'perfmon'
+Requires-Dist: dash>=2.18.2; extra == 'perfmon'
+Requires-Dist: ezmsg-baseproc; extra == 'perfmon'
+Requires-Dist: pandas>=2.2.3; extra == 'perfmon'
+Requires-Dist: plotly>=5.24.1; extra == 'perfmon'
+Requires-Dist: pygtail>=0.14.0; extra == 'perfmon'
+Requires-Dist: typer>=0.15.1; extra == 'perfmon'
+Provides-Extra: sigmon
+Requires-Dist: pygame>=2.6.1; extra == 'sigmon'
+Requires-Dist: pygraphviz>=1.14; extra == 'sigmon'
+Requires-Dist: typer>=0.15.1; extra == 'sigmon'
+Description-Content-Type: text/markdown
+
+# ezmsg-tools
+
+A namespace package for [ezmsg](https://github.com/iscoe/ezmsg) to visualize running graphs and data.
+
+The data visualization is highly fragile. Expect bugs.
+
+## Installation
+
+### Pre-requisites
+
+* [graphviz](https://graphviz.org/download/)
+
+On Mac, you should use brew:
+
+* `brew install graphviz`
+* `export CFLAGS="-I $(brew --prefix graphviz)/include"`
+* `export LDFLAGS="-L $(brew --prefix graphviz)/lib"`
+
+### Release
+
+Install the latest release from pypi with: `pip install ezmsg-tools` (or `uv add ...` or `poetry add ...`).
+
+More than likely, you will want to include at least one of the extras when installing:
+
+`pip install "ezmsg-tools[all]"`
+
+### Development Version
+
+If you intend to edit `ezmsg-tools` then please refer to the [Developers](#developers) section below.
+
+You can add the development version of ezmsg-tools directly from GitHub:
+
+* Using `pip`: `pip install git+https://github.com/ezmsg-org/ezmsg-tools.git@dev`
+* Using `poetry`: `poetry add "git+https://github.com/ezmsg-org/ezmsg-tools.git@dev"`
+* Using `uv`: `uv add git+https://github.com/ezmsg-org/ezmsg-tools --branch dev`
+
+You probably want to include the extras when installing the development version:
+
+* `pip install "ezmsg-tools[all] @ git+https://github.com/ezmsg-org/ezmsg-tools.git@dev"`
+
+## Getting Started
+
+This package includes some entrypoints with useful tools.
+
+### ezmsg-performance-monitor
+
+This tool operates on logfiles created by ezmsg. Logfiles will automatically be created when running a pipeline containing nodes decorated with `ezmsg.sigproc.util.profile.profile_subpub`,
+and if the `EZMSG_LOGLEVEL` environment variable is set to DEBUG. The logfiles will be created in `~/.ezmsg/profile/ezprofiler.log` by default but this can be changed with the `EZMSG_PROFILE` environment variable.
+
+Most of the nodes provided by `ezmsg.sigproc` are already decorated to enable profiling, as is any custom nodes that inherit from `ezmsg.sigproc.base.GenAxisArray`.
+You can decorate other nodes with `ezmsg.sigproc.util.profile.profile_subpub` to enable profiling.
+
+During a run with profiling enabled, the logfiles will be created in the specified location. You may wish to additionally create a graph file: (`uv run`) `EZMSG_LOGLEVEL=WARN ezmsg mermaid > ~/.ezmsg/profile/ezprofiler.mermaid`
+
+During or after a pipeline run with profiling enabled, you can run (`uv run `) `performance-monitor` to visualize the performance of the nodes in the pipeline.
+
+> Unlike `signal-monitor`, this tool does not require the pipeline to attach to an existing graph service because it relies exclusively on the logfile.
+
+### ezmsg-signal-monitor
+
+The pipeline must be running on a graph service exposed on the network. For example, first, run the GraphService on an open port:
+
+`ezmsg --address 127.0.0.1:25978 start`
+
+Then run your usual pipeline but make sure it attaches to the graph address by passing `graph_address=("127.0.0.1", 25978)` as a kwarg to `ez.run`.
+
+While the pipeline is running, you can run the signal-monitor tool with (`uv run`) `signal-monitor --graph-addr 127.0.0.1:25978`.
+
+This launches a window with graph visualized on the left. Click on a node's output box to get a live visualization on the right side of the screen plotting the data as it leaves that node. Use `a` to toggle auto-scaling. With auto-scaling off, use `-`, and `=` to zoom out and in, respectively.
+
+> Currently only 2-D outputs are supported!
+
+Don't forget to shutdown your graph service when you are done, e.g.: `ezmsg --address 127.0.0.1:25978 shutdown` 
+
+## Developers
+
+We use [`uv`](https://docs.astral.sh/uv/getting-started/installation/) for development. It is not strictly required, but if you intend to contribute to ezmsg-tools then using `uv` will lead to the smoothest collaboration.
+
+1. Install [`uv`](https://docs.astral.sh/uv/getting-started/installation/) if not already installed.
+2. Fork ezmsg-tools and clone your fork to your local computer.
+3. Open a terminal and `cd` to the cloned folder.
+4. Make sure `pygraphviz` [pre-requisites](#pre-requisites) are installed.
+    * On mac: `export CFLAGS="-I $(brew --prefix graphviz)/include"` and `export LDFLAGS="-L $(brew --prefix graphviz)/lib"`
+5. `uv sync --all-extras --python 3.10` to create a .venv and install ezmsg-tools including dev and test dependencies.
+6. After editing code and making commits, Run the test suite before making a PR: `uv run pytest`
+
+## Troubleshooting
+
+Graphviz can be difficult to install on some systems. The simplest may be to use conda/mamba: `conda install graphviz`.
+If that fails, [see here](https://github.com/pygraphviz/pygraphviz/issues/398#issuecomment-1038476921).

ezmsg_tools-0.1.0/README.md

@@ -0,0 +1,90 @@
+# ezmsg-tools
+
+A namespace package for [ezmsg](https://github.com/iscoe/ezmsg) to visualize running graphs and data.
+
+The data visualization is highly fragile. Expect bugs.
+
+## Installation
+
+### Pre-requisites
+
+* [graphviz](https://graphviz.org/download/)
+
+On Mac, you should use brew:
+
+* `brew install graphviz`
+* `export CFLAGS="-I $(brew --prefix graphviz)/include"`
+* `export LDFLAGS="-L $(brew --prefix graphviz)/lib"`
+
+### Release
+
+Install the latest release from pypi with: `pip install ezmsg-tools` (or `uv add ...` or `poetry add ...`).
+
+More than likely, you will want to include at least one of the extras when installing:
+
+`pip install "ezmsg-tools[all]"`
+
+### Development Version
+
+If you intend to edit `ezmsg-tools` then please refer to the [Developers](#developers) section below.
+
+You can add the development version of ezmsg-tools directly from GitHub:
+
+* Using `pip`: `pip install git+https://github.com/ezmsg-org/ezmsg-tools.git@dev`
+* Using `poetry`: `poetry add "git+https://github.com/ezmsg-org/ezmsg-tools.git@dev"`
+* Using `uv`: `uv add git+https://github.com/ezmsg-org/ezmsg-tools --branch dev`
+
+You probably want to include the extras when installing the development version:
+
+* `pip install "ezmsg-tools[all] @ git+https://github.com/ezmsg-org/ezmsg-tools.git@dev"`
+
+## Getting Started
+
+This package includes some entrypoints with useful tools.
+
+### ezmsg-performance-monitor
+
+This tool operates on logfiles created by ezmsg. Logfiles will automatically be created when running a pipeline containing nodes decorated with `ezmsg.sigproc.util.profile.profile_subpub`,
+and if the `EZMSG_LOGLEVEL` environment variable is set to DEBUG. The logfiles will be created in `~/.ezmsg/profile/ezprofiler.log` by default but this can be changed with the `EZMSG_PROFILE` environment variable.
+
+Most of the nodes provided by `ezmsg.sigproc` are already decorated to enable profiling, as is any custom nodes that inherit from `ezmsg.sigproc.base.GenAxisArray`.
+You can decorate other nodes with `ezmsg.sigproc.util.profile.profile_subpub` to enable profiling.
+
+During a run with profiling enabled, the logfiles will be created in the specified location. You may wish to additionally create a graph file: (`uv run`) `EZMSG_LOGLEVEL=WARN ezmsg mermaid > ~/.ezmsg/profile/ezprofiler.mermaid`
+
+During or after a pipeline run with profiling enabled, you can run (`uv run `) `performance-monitor` to visualize the performance of the nodes in the pipeline.
+
+> Unlike `signal-monitor`, this tool does not require the pipeline to attach to an existing graph service because it relies exclusively on the logfile.
+
+### ezmsg-signal-monitor
+
+The pipeline must be running on a graph service exposed on the network. For example, first, run the GraphService on an open port:
+
+`ezmsg --address 127.0.0.1:25978 start`
+
+Then run your usual pipeline but make sure it attaches to the graph address by passing `graph_address=("127.0.0.1", 25978)` as a kwarg to `ez.run`.
+
+While the pipeline is running, you can run the signal-monitor tool with (`uv run`) `signal-monitor --graph-addr 127.0.0.1:25978`.
+
+This launches a window with graph visualized on the left. Click on a node's output box to get a live visualization on the right side of the screen plotting the data as it leaves that node. Use `a` to toggle auto-scaling. With auto-scaling off, use `-`, and `=` to zoom out and in, respectively.
+
+> Currently only 2-D outputs are supported!
+
+Don't forget to shutdown your graph service when you are done, e.g.: `ezmsg --address 127.0.0.1:25978 shutdown` 
+
+## Developers
+
+We use [`uv`](https://docs.astral.sh/uv/getting-started/installation/) for development. It is not strictly required, but if you intend to contribute to ezmsg-tools then using `uv` will lead to the smoothest collaboration.
+
+1. Install [`uv`](https://docs.astral.sh/uv/getting-started/installation/) if not already installed.
+2. Fork ezmsg-tools and clone your fork to your local computer.
+3. Open a terminal and `cd` to the cloned folder.
+4. Make sure `pygraphviz` [pre-requisites](#pre-requisites) are installed.
+    * On mac: `export CFLAGS="-I $(brew --prefix graphviz)/include"` and `export LDFLAGS="-L $(brew --prefix graphviz)/lib"`
+5. `uv sync --all-extras --python 3.10` to create a .venv and install ezmsg-tools including dev and test dependencies.
+6. After editing code and making commits, Run the test suite before making a PR: `uv run pytest`
+
+## Troubleshooting
+
+Graphviz can be difficult to install on some systems. The simplest may be to use conda/mamba: `conda install graphviz`.
+If that fails, [see here](https://github.com/pygraphviz/pygraphviz/issues/398#issuecomment-1038476921).

ezmsg_tools-0.1.0/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = source
+BUILDDIR      = build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

ezmsg_tools-0.1.0/docs/make.bat

@@ -0,0 +1,35 @@
+@ECHO OFF
+
+pushd %~dp0
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+	set SPHINXBUILD=sphinx-build
+)
+set SOURCEDIR=source
+set BUILDDIR=build
+
+if "%1" == "" goto help
+
+%SPHINXBUILD% >NUL 2>NUL
+if errorlevel 9009 (
+	echo.
+	echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
+	echo.installed, then set the SPHINXBUILD environment variable to point
+	echo.to the full path of the 'sphinx-build' executable. Alternatively you
+	echo.may add the Sphinx directory to PATH.
+	echo.
+	echo.If you don't have Sphinx installed, grab it from
+	echo.http://sphinx-doc.org/
+	exit /b 1
+)
+
+%SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+goto end
+
+:help
+%SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+
+:end
+popd

ezmsg_tools-0.1.0/docs/source/_templates/autosummary/module.rst

@@ -0,0 +1,64 @@
+{{ fullname | escape | underline}}
+
+.. automodule:: {{ fullname }}
+
+   {% block attributes %}
+   {% if attributes %}
+   .. rubric:: Module Attributes
+
+   .. autosummary::
+      :toctree:
+   {% for item in attributes %}
+      {{ item }}
+   {%- endfor %}
+   {% endif %}
+   {% endblock %}
+
+   {% block functions %}
+   {% if functions %}
+   .. rubric:: Functions
+
+   {% for item in functions %}
+   .. autofunction:: {{ item }}
+   {%- endfor %}
+   {% endif %}
+   {% endblock %}
+
+   {% block classes %}
+   {% if classes %}
+   .. rubric:: Classes
+
+   {% for item in classes %}
+   .. autoclass:: {{ item }}
+      :members:
+      :undoc-members:
+      :show-inheritance:
+      :special-members: __init__
+   {%- endfor %}
+   {% endif %}
+   {% endblock %}
+
+   {% block exceptions %}
+   {% if exceptions %}
+   .. rubric:: Exceptions
+
+   {% for item in exceptions %}
+   .. autoexception:: {{ item }}
+      :members:
+      :show-inheritance:
+   {%- endfor %}
+   {% endif %}
+   {% endblock %}
+
+{% block modules %}
+{% if modules %}
+.. rubric:: Modules
+
+.. autosummary::
+   :toctree:
+   :recursive:
+{% for item in modules %}
+   {{ item }}
+{%- endfor %}
+{% endif %}
+{% endblock %}

ezmsg_tools-0.1.0/docs/source/api/index.rst

@@ -0,0 +1,11 @@
+API Reference
+=============
+
+This page contains auto-generated API reference documentation.
+
+.. autosummary::
+   :toctree: generated
+   :recursive:
+   :template: autosummary/module.rst
+
+   ezmsg.tools

ezmsg_tools-0.1.0/docs/source/conf.py

@@ -0,0 +1,121 @@
+# Configuration file for the Sphinx documentation builder.
+
+import os
+import sys
+
+# Add the source directory to the path
+sys.path.insert(0, os.path.abspath("../../src"))
+
+# -- Project information --------------------------
+
+project = "ezmsg.tools"
+copyright = "2025, ezmsg Contributors"
+author = "ezmsg Contributors"
+
+# The version is managed by hatch-vcs and stored in __version__.py
+try:
+    from ezmsg.tools.__version__ import version as release
+except ImportError:
+    release = "unknown"
+
+# For display purposes, extract the base version without git commit info
+version = release.split("+")[0] if release != "unknown" else release
+
+# -- General configuration --------------------------
+
+extensions = [
+    "sphinx.ext.autodoc",
+    "sphinx.ext.autosummary",
+    "sphinx.ext.napoleon",
+    "sphinx.ext.intersphinx",
+    "sphinx.ext.viewcode",
+    "sphinx.ext.duration",
+    "sphinx_copybutton",
+    "myst_parser",  # For markdown files
+]
+
+templates_path = ["_templates"]
+source_suffix = {
+    ".rst": "restructuredtext",
+    ".md": "markdown",
+}
+exclude_patterns = ["_build", "Thumbs.db", ".DS_Store"]
+
+# The toctree master document
+master_doc = "index"
+
+# -- Autodoc configuration ------------------------------
+
+# Auto-generate API docs
+autosummary_generate = True
+autosummary_imported_members = False
+autodoc_typehints = "description"
+autodoc_member_order = "bysource"
+autodoc_typehints_format = "short"
+python_use_unqualified_type_names = True
+autodoc_default_options = {
+    "members": True,
+    "member-order": "bysource",
+    "special-members": "__init__",
+    "undoc-members": True,
+    "show-inheritance": True,
+}
+
+# Don't show the full module path in the docs
+add_module_names = False
+
+# -- Intersphinx configuration --------------------------
+
+intersphinx_mapping = {
+    "python": ("https://docs.python.org/3/", None),
+    "numpy": ("https://numpy.org/doc/stable/", None),
+    "ezmsg": ("https://www.ezmsg.org/ezmsg/", None),
+}
+intersphinx_disabled_domains = ["std"]
+
+# -- Options for HTML output -----------------------------
+
+html_theme = "pydata_sphinx_theme"
+html_static_path = ["_static"]
+
+# Set the base URL for the documentation
+html_baseurl = "https://www.ezmsg.org/ezmsg-tools/"
+
+html_theme_options = {
+    "logo": {
+        "text": f"ezmsg.tools {version}",
+        "link": "https://ezmsg.org",  # Link back to main site
+    },
+    "header_links_before_dropdown": 4,
+    "navbar_start": ["navbar-logo"],
+    "navbar_end": ["theme-switcher", "navbar-icon-links"],
+    "icon_links": [
+        {
+            "name": "GitHub",
+            "url": "https://github.com/ezmsg-org/ezmsg-tools",
+            "icon": "fa-brands fa-github",
+        },
+        {
+            "name": "ezmsg.org",
+            "url": "https://www.ezmsg.org",
+            "icon": "fa-solid fa-house",
+        },
+    ],
+}
+
+# Timestamp is inserted at every page bottom in this strftime format.
+html_last_updated_fmt = "%Y-%m-%d"
+
+# -- Options for linkcode -----------------------------
+
+branch = "main"
+code_url = f"https://github.com/ezmsg-org/ezmsg-tools/blob/{branch}/"
+
+
+def linkcode_resolve(domain, info):
+    if domain != "py":
+        return None
+    if not info["module"]:
+        return None
+    filename = info["module"].replace(".", "/")
+    return f"{code_url}src/{filename}.py"