dbt-tree 0.1.0__tar.gz

dbt_tree-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - name: Lint (ruff)
+        run: ruff check src tests
+      - name: Unit tests
+        run: pytest -q

dbt_tree-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,67 @@
+name: release
+
+# Publishes to PyPI via Trusted Publishing (OIDC) — no API tokens needed.
+# Fires when you publish a GitHub Release (e.g. for tag v0.1.0).
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: "Publish target"
+        type: choice
+        default: testpypi
+        options: [testpypi, pypi]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: python -m pip install --upgrade build twine
+      - run: python -m build
+      - run: python -m twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-pypi:
+    # Real PyPI on a published release, or manual dispatch with target=pypi.
+    if: github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && inputs.target == 'pypi')
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/dbt-tree
+    permissions:
+      id-token: write   # required for Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  publish-testpypi:
+    # Dry-run channel: manual dispatch with target=testpypi (the default).
+    if: github.event_name == 'workflow_dispatch' && inputs.target == 'testpypi'
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: testpypi
+      url: https://test.pypi.org/p/dbt-tree
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/

dbt_tree-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+*.egg-info/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.DS_Store

dbt_tree-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dbt_tree-0.1.0/Makefile

@@ -0,0 +1,13 @@
+.PHONY: install test lint fmt
+
+install:
+	pip install -e ".[dev]"
+
+test:
+	pytest -q
+
+lint:
+	ruff check .
+
+fmt:
+	ruff format .

dbt_tree-0.1.0/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: dbt-tree
+Version: 0.1.0
+Summary: Pretty terminal lineage tree for dbt selectors (dbt-tree "model+").
+Project-URL: Homepage, https://github.com/KarthikRajashekaran/dbt-tree
+Project-URL: Issues, https://github.com/KarthikRajashekaran/dbt-tree/issues
+Author: Karthik Rajashekaran
+License: Apache-2.0
+License-File: LICENSE
+Keywords: cli,dag,data-engineering,dbt,lineage,tree
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: rich>=13.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# dbt-tree
+
+Pretty terminal lineage tree for dbt selectors. Run a selector, get a readable
+tree of the resulting DAG right in your terminal — no docs server, no browser.
+
+```bash
+dbt-tree "my_model+"
+```
+
+`dbt-tree` forwards the selector **verbatim** to `dbt ls`, so every dbt selector
+works exactly as it does in dbt itself: `model+`, `+model`, `+model+`,
+`2+model+3`, `tag:nightly+`, `path:models/marts`, set unions, and so on.
+
+## Requirements
+
+- A working **dbt-core** install that you can run as `dbt` (any virtualenv tool is
+  fine — `venv`, `virtualenv`, `conda`, `poetry`, `uv`, …). The only requirement
+  is that the `dbt` executable is reachable (active venv, on `PATH`, or via
+  `$DBT_TREE_DBT` / `--dbt-executable`).
+- Python 3.10+.
+
+`dbt ls` is parse-only, so **no warehouse connection is needed** to draw the tree.
+
+## Install
+
+Install into the **same environment as your dbt** so they share a `PATH`:
+
+```bash
+pip install dbt-tree           # once published
+# or, from source:
+pip install "git+https://github.com/KarthikRajashekaran/dbt-tree.git"
+```
+
+`dbt` itself is **not** a Python dependency — `dbt-tree` shells out to your
+existing dbt rather than pinning a version.
+
+### Which dbt does it use?
+
+Resolution order:
+
+1. `--dbt-executable`
+2. `$DBT_TREE_DBT`
+3. **the active virtualenv** (`$VIRTUAL_ENV/bin/dbt`) — so once you activate your
+   dbt venv, dbt-tree uses the same dbt as your shell
+4. `dbt` on `PATH`
+
+dbt-tree prefers **dbt-core** and will skip a **dbt Fusion** binary when a core
+install is available (Fusion's stricter parsing and different `ls` surface aren't
+supported yet). 
+
+### Recommended workflow:
+
+```bash
+gva # activate your dbt venv (dbt-core)
+dbt-tree "my_model+"
+```
+
+Tip: `pip install` dbt-tree *into that same dbt venv* so `gva` puts both `dbt` and
+`dbt-tree` on your `PATH` together.
+
+## Usage
+
+```bash
+# Downstream lineage
+dbt-tree "my_model+"
+
+# Upstream lineage
+dbt-tree "+my_model"
+
+# Scope / dbt passthrough
+dbt-tree "tag:nightly+" --target prod --project-dir dbt/my_project
+```
+
+Example output:
+
+```text
+my_model (view) *
+└── stg_orders (table)
+    └── int_orders_joined (table)
+        ├── fct_orders (table)
+        │   ├── mart_revenue (table)
+        │   └── ...
+        └── fct_order_items (table)
+```
+
+The originally-selected model is marked with `*`. Nodes are colored by resource
+type; the suffix shows materialization (`table`/`view`) or resource type
+(`source`/`seed`/`snapshot`).
+
+### Orientation follows the selector
+
+The tree is rooted so the focal model is always at the top:
+
+- `model+` (downstream) — root is the model, children are its descendants.
+- `+model` (upstream) — root is the model, children are its **ancestors** (up to
+  sources/seeds).
+- `+model+` (both) — two sections: `▲ ancestors` then `▼ descendants`.
+
+## How it works
+
+1. Runs `dbt --quiet ls --output json --output-keys ... --select <selector>`.
+2. Keeps models, sources, seeds, and snapshots (tests off unless `--include-tests`).
+3. Builds child adjacency **within the selected set**, finds roots, and expands a
+   duplicated tree (Unix `tree` style) with cycle and node-count guards.
+4. Renders a `rich` tree (duplicating shared subtrees, `tree`-command style).
+
+## Options
+
+| flag | default | meaning |
+|---|---|---|
+| `--target` | — | dbt target |
+| `--project-dir` | — | dbt project directory |
+| `--profiles-dir` | — | dbt profiles directory |
+| `--dbt-executable` | `dbt` | path to dbt |
+| `--include-tests` | off | include data/unit tests as nodes |
+| `--max-depth` | `0` | limit depth (0 = unlimited) |
+| `--max-nodes` | `5000` | safety cap on rendered nodes |
+| `--no-color` | off | disable color in plain output |
+
+Unknown flags are forwarded to `dbt ls` as an escape hatch.
+
+## Limitations
+
+- **Single project.** Lineage covers whatever `dbt ls` resolves in the active
+  project; it does not stitch across sibling projects in a monorepo.
+- Selector parsing is dbt's, so behavior matches your installed dbt version.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest
+ruff check .
+```
+
+## License
+
+Apache-2.0

dbt_tree-0.1.0/README.md

@@ -0,0 +1,138 @@
+# dbt-tree
+
+Pretty terminal lineage tree for dbt selectors. Run a selector, get a readable
+tree of the resulting DAG right in your terminal — no docs server, no browser.
+
+```bash
+dbt-tree "my_model+"
+```
+
+`dbt-tree` forwards the selector **verbatim** to `dbt ls`, so every dbt selector
+works exactly as it does in dbt itself: `model+`, `+model`, `+model+`,
+`2+model+3`, `tag:nightly+`, `path:models/marts`, set unions, and so on.
+
+## Requirements
+
+- A working **dbt-core** install that you can run as `dbt` (any virtualenv tool is
+  fine — `venv`, `virtualenv`, `conda`, `poetry`, `uv`, …). The only requirement
+  is that the `dbt` executable is reachable (active venv, on `PATH`, or via
+  `$DBT_TREE_DBT` / `--dbt-executable`).
+- Python 3.10+.
+
+`dbt ls` is parse-only, so **no warehouse connection is needed** to draw the tree.
+
+## Install
+
+Install into the **same environment as your dbt** so they share a `PATH`:
+
+```bash
+pip install dbt-tree           # once published
+# or, from source:
+pip install "git+https://github.com/KarthikRajashekaran/dbt-tree.git"
+```
+
+`dbt` itself is **not** a Python dependency — `dbt-tree` shells out to your
+existing dbt rather than pinning a version.
+
+### Which dbt does it use?
+
+Resolution order:
+
+1. `--dbt-executable`
+2. `$DBT_TREE_DBT`
+3. **the active virtualenv** (`$VIRTUAL_ENV/bin/dbt`) — so once you activate your
+   dbt venv, dbt-tree uses the same dbt as your shell
+4. `dbt` on `PATH`
+
+dbt-tree prefers **dbt-core** and will skip a **dbt Fusion** binary when a core
+install is available (Fusion's stricter parsing and different `ls` surface aren't
+supported yet). 
+
+### Recommended workflow:
+
+```bash
+gva # activate your dbt venv (dbt-core)
+dbt-tree "my_model+"
+```
+
+Tip: `pip install` dbt-tree *into that same dbt venv* so `gva` puts both `dbt` and
+`dbt-tree` on your `PATH` together.
+
+## Usage
+
+```bash
+# Downstream lineage
+dbt-tree "my_model+"
+
+# Upstream lineage
+dbt-tree "+my_model"
+
+# Scope / dbt passthrough
+dbt-tree "tag:nightly+" --target prod --project-dir dbt/my_project
+```
+
+Example output:
+
+```text
+my_model (view) *
+└── stg_orders (table)
+    └── int_orders_joined (table)
+        ├── fct_orders (table)
+        │   ├── mart_revenue (table)
+        │   └── ...
+        └── fct_order_items (table)
+```
+
+The originally-selected model is marked with `*`. Nodes are colored by resource
+type; the suffix shows materialization (`table`/`view`) or resource type
+(`source`/`seed`/`snapshot`).
+
+### Orientation follows the selector
+
+The tree is rooted so the focal model is always at the top:
+
+- `model+` (downstream) — root is the model, children are its descendants.
+- `+model` (upstream) — root is the model, children are its **ancestors** (up to
+  sources/seeds).
+- `+model+` (both) — two sections: `▲ ancestors` then `▼ descendants`.
+
+## How it works
+
+1. Runs `dbt --quiet ls --output json --output-keys ... --select <selector>`.
+2. Keeps models, sources, seeds, and snapshots (tests off unless `--include-tests`).
+3. Builds child adjacency **within the selected set**, finds roots, and expands a
+   duplicated tree (Unix `tree` style) with cycle and node-count guards.
+4. Renders a `rich` tree (duplicating shared subtrees, `tree`-command style).
+
+## Options
+
+| flag | default | meaning |
+|---|---|---|
+| `--target` | — | dbt target |
+| `--project-dir` | — | dbt project directory |
+| `--profiles-dir` | — | dbt profiles directory |
+| `--dbt-executable` | `dbt` | path to dbt |
+| `--include-tests` | off | include data/unit tests as nodes |
+| `--max-depth` | `0` | limit depth (0 = unlimited) |
+| `--max-nodes` | `5000` | safety cap on rendered nodes |
+| `--no-color` | off | disable color in plain output |
+
+Unknown flags are forwarded to `dbt ls` as an escape hatch.
+
+## Limitations
+
+- **Single project.** Lineage covers whatever `dbt ls` resolves in the active
+  project; it does not stitch across sibling projects in a monorepo.
+- Selector parsing is dbt's, so behavior matches your installed dbt version.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest
+ruff check .
+```
+
+## License
+
+Apache-2.0

dbt_tree-0.1.0/pyproject.toml

@@ -0,0 +1,51 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "dbt-tree"
+version = "0.1.0"
+description = "Pretty terminal lineage tree for dbt selectors (dbt-tree \"model+\")."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Karthik Rajashekaran" }]
+keywords = [
+    "dbt",
+    "lineage",
+    "dag",
+    "tree",
+    "cli",
+    "data-engineering",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development :: Build Tools",
+    "Topic :: Utilities",
+]
+dependencies = ["rich>=13.0"]
+
+[project.optional-dependencies]
+dev = ["pytest>=7.4", "ruff>=0.4"]
+
+[project.scripts]
+dbt-tree = "dbt_tree.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/KarthikRajashekaran/dbt-tree"
+Issues = "https://github.com/KarthikRajashekaran/dbt-tree/issues"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/dbt_tree"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"

dbt_tree-0.1.0/src/dbt_tree/__init__.py

@@ -0,0 +1,3 @@
+"""dbt-tree: interactive terminal lineage tree for dbt selectors."""
+
+__version__ = "0.1.0"