3 A library

3.1 A library, with uv init

uv init --lib makes a library. In a folder of a project, it also makes the library a member of the project's workspace. --author-from none leaves out the name of the author, which uv would take from your git settings.

The author ran uv init --lib --author-from none packages/talib here. It writes packages/talib/README.md, packages/talib/pyproject.toml, packages/talib/src/talib/__init__.py, packages/talib/src/talib/py.typed and pyproject.toml. On a later day, it can write newer versions of packages than the author's, and then git check finds that your files differ. So do not run it. Run this command in its place, from the top of the project. It takes each file as the author has it from the project:

git restore --source f154823215af -- packages/talib/README.md packages/talib/pyproject.toml packages/talib/src/talib/__init__.py packages/talib/src/talib/py.typed pyproject.toml

uv.lock does not name talib yet, so it is out of date until the next move. A uv run would lock it again, so the check reads the file:

grep -A2 'tool.uv.workspace' pyproject.toml

It prints the table [tool.uv.workspace], with members = [ and "packages/talib", under it.

Check your files against this move. The command prints nothing when they match, and otherwise shows what differs:

git check f154823215af

If you are stuck, this command puts the files of this move in place of yours. A file that you made yourself stays:

git restore --source d6f47209c66d --staged -- :/ && git restore --source f154823215af --staged --worktree -- :/

@@ -0,0 +1,11 @@
+[project]
+name = "talib"
+version = "0.1.0"
+description = "Add your description here"
+readme = "README.md"
+requires-python = ">=3.12"
+dependencies = []
+
+[build-system]
+requires = ["uv_build>=0.12.13,<0.13.0"]
+build-backend = "uv_build"

@@ -0,0 +1,2 @@
+def hello() -> str:
+    return "Hello from talib!"

@@ -28,3 +28,8 @@ line-length = 100
 
 [tool.uv]
 default-groups = ["dev", "docs"]
+
+[tool.uv.workspace]
+members = [
+    "packages/talib",
+]

3.2 tally depends on talib

tally cannot import talib until it depends on it. uv add finds talib in the workspace, and takes it from there:

The author ran uv add talib here. It writes pyproject.toml and uv.lock. On a later day, it can write newer versions of packages than the author's, and then git check finds that your files differ. So do not run it. Run this command in its place, from the top of the project. It takes each file as the author has it from the project, and installs exactly the versions that uv.lock names:

git restore --source de7bf1a4a64c -- pyproject.toml uv.lock && uv sync --locked --all-groups --all-packages

uv run python -c "import talib; print(talib.hello())"

It prints Hello from talib!.

Check your files against this move. The command prints nothing when they match, and otherwise shows what differs:

git check de7bf1a4a64c

If you are stuck, this command puts the files of this move in place of yours. A file that you made yourself stays:

git restore --source f154823215af --staged -- :/ && git restore --source de7bf1a4a64c --staged --worktree -- :/

@@ -6,6 +6,7 @@ readme = "README.md"
 requires-python = ">=3.12"
 dependencies = [
     "tabulate>=0.9,<0.10",
+    "talib",
 ]
 
 [project.scripts]
@@ -33,3 +34,6 @@ default-groups = ["dev", "docs"]
 members = [
     "packages/talib",
 ]
+
+[tool.uv.sources]
+talib = { workspace = true }

3.3 top goes into talib

top is still in tally, and talib has only hello. One patch moves top across, in both packages.

Apply the patch to packages/talib/src/talib/__init__.py, from the top of the project:

curl -fsSL https://github.com/rahuldave/tally/commit/909df18d1c02f51f42154cdded5a8ef515482057.diff | git apply --include=packages/talib/src/talib/__init__.py

Apply the patch to src/tally/__init__.py, from the top of the project:

curl -fsSL https://github.com/rahuldave/tally/commit/909df18d1c02f51f42154cdded5a8ef515482057.diff | git apply --include=src/tally/__init__.py

In packages/talib/src/talib/__init__.py, the patch puts a docstring and top in place of hello. In src/tally/__init__.py, it removes top, and adds from talib import top under from tabulate import tabulate.

uv run python -m unittest discover -s tests -q

All four tests pass.

head -4 packages/talib/src/talib/__init__.py

"""talib: small helpers for the counts of words."""


def top(counts: dict[str, int], n: int) -> list[tuple[str, int]]:

It prints the docstring of the library, two blank lines, and the first line of top.

Check your files against this move. The command prints nothing when they match, and otherwise shows what differs:

git check 909df18d1c02

If you are stuck, this command puts the files of this move in place of yours. A file that you made yourself stays:

git restore --source de7bf1a4a64c --staged -- :/ && git restore --source 909df18d1c02 --staged --worktree -- :/

@@ -1,2 +1,6 @@
-def hello() -> str:
-    return "Hello from talib!"
+"""talib: small helpers for the counts of words."""
+
+
+def top(counts: dict[str, int], n: int) -> list[tuple[str, int]]:
+    "The n most common words, most common first."
+    return sorted(counts.items(), key=lambda pair: (-pair[1], pair[0]))[:n]

@@ -3,6 +3,7 @@
 import sys
 
 from tabulate import tabulate
+from talib import top
 
 
 def count(text: str) -> dict[str, int]:
@@ -13,11 +14,6 @@ def count(text: str) -> dict[str, int]:
     return counts
 
 
-def top(counts: dict[str, int], n: int) -> list[tuple[str, int]]:
-    "The n most common words, most common first."
-    return sorted(counts.items(), key=lambda pair: (-pair[1], pair[0]))[:n]
-
-
 def main() -> None:
     "Count the words of a file, or of the standard input. Options: --top N, and --table."
     args = sys.argv[1:]