hanky 0.3.0.dev1__tar.gz → 0.3.0.dev3__tar.gz

{hanky-0.3.0.dev1 → hanky-0.3.0.dev3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hanky
-Version: 0.3.0.dev1
+Version: 0.3.0.dev3
 Summary: Simple library and command line tool for loading flash cards into anki.
 Project-URL: Homepage, https://github.com/Haeata-Ash/hanky
 Project-URL: Issues, https://github.com/Haeata-Ash/hanky/issues
@@ -103,7 +103,7 @@ We would run our new script like so
 python3 my_script.py pipe words.csv --into english::vocab
 ```
 
-Here we tell hanky to **pipe** each word in `words.csv` through our `card_processors`, **transforming** each line of the csv with the `lowercase_card`, before finally adding each card, of note type `basic` (the model we set on the pipeline), into the anki deck `english::vocab`. A single run can target a different model by passing `--model`.
+Here we tell hanky to **pipe** each word in `words.csv` through our `card_processors`, **transforming** each line of the csv with the `lowercase_card`, before finally adding each card, of note type `basic` (the model we gave to the pipeline), into the anki deck `english::vocab`.
 
 This would leave us with a **english::vocab** deck containing the following cards:
 
@@ -168,10 +168,6 @@ Multiple processors can be registered on a `HankyPipeline` app to create a pipel
 
 ### The processor contract
 
-Processors are model-agnostic: the Anki model/note-type is set once on the
-pipeline itself (`HankyPipeline("basic")`), and every card the pipeline adds is
-created with that model (unless overridden for a run with `--model`).
-
 A processor is registered with two things:
 
 ```python
@@ -373,10 +369,9 @@ Both the `hanky` command and your own scripts share the same interface:
 [hanky | python3 my_script.py] <operation> <file|dir> [pattern] [options]
 ```
 
-Cards are created with the model set on the pipeline (`HankyPipeline("basic")`);
-pass `-m/--model` to override it for a single run. The standalone `hanky`
-command has no script of its own, so it uses Anki's built-in `Basic` model
-unless you override it.
+Note that cards are created with the model set on the pipeline (`HankyPipeline("my-model")`). 
+Since standalone `hanky` command has no script of its own, it uses Anki's built-in 
+`Basic` model unless you override it.
 
 **`pipe`** — pipe cards from a single file into a deck:
 

{hanky-0.3.0.dev1 → hanky-0.3.0.dev3}/README.md

@@ -85,7 +85,7 @@ We would run our new script like so
 python3 my_script.py pipe words.csv --into english::vocab
 ```
 
-Here we tell hanky to **pipe** each word in `words.csv` through our `card_processors`, **transforming** each line of the csv with the `lowercase_card`, before finally adding each card, of note type `basic` (the model we set on the pipeline), into the anki deck `english::vocab`. A single run can target a different model by passing `--model`.
+Here we tell hanky to **pipe** each word in `words.csv` through our `card_processors`, **transforming** each line of the csv with the `lowercase_card`, before finally adding each card, of note type `basic` (the model we gave to the pipeline), into the anki deck `english::vocab`.
 
 This would leave us with a **english::vocab** deck containing the following cards:
 
@@ -150,10 +150,6 @@ Multiple processors can be registered on a `HankyPipeline` app to create a pipel
 
 ### The processor contract
 
-Processors are model-agnostic: the Anki model/note-type is set once on the
-pipeline itself (`HankyPipeline("basic")`), and every card the pipeline adds is
-created with that model (unless overridden for a run with `--model`).
-
 A processor is registered with two things:
 
 ```python
@@ -355,10 +351,9 @@ Both the `hanky` command and your own scripts share the same interface:
 [hanky | python3 my_script.py] <operation> <file|dir> [pattern] [options]
 ```
 
-Cards are created with the model set on the pipeline (`HankyPipeline("basic")`);
-pass `-m/--model` to override it for a single run. The standalone `hanky`
-command has no script of its own, so it uses Anki's built-in `Basic` model
-unless you override it.
+Note that cards are created with the model set on the pipeline (`HankyPipeline("my-model")`). 
+Since standalone `hanky` command has no script of its own, it uses Anki's built-in 
+`Basic` model unless you override it.
 
 **`pipe`** — pipe cards from a single file into a deck:
 

{hanky-0.3.0.dev1 → hanky-0.3.0.dev3}/pyproject.toml

@@ -16,7 +16,7 @@ classifiers = [
 ]
 
 keywords = ["anki"]
-version = "0.3.0.dev1"
+version = "0.3.0.dev3"
 
 dependencies = [
   "anki",

{hanky-0.3.0.dev1 → hanky-0.3.0.dev3}/uv.lock

@@ -398,7 +398,7 @@ wheels = [
 
 [[package]]
 name = "hanky"
-version = "0.3.0.dev1"
+version = "0.3.0.dev3"
 source = { editable = "." }
 dependencies = [
     { name = "anki" },