sqlite-export-for-ynab 2.9.5__tar.gz → 2.9.7__tar.gz

{sqlite_export_for_ynab-2.9.5/sqlite_export_for_ynab.egg-info → sqlite_export_for_ynab-2.9.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlite_export_for_ynab
-Version: 2.9.5
+Version: 2.9.7
 Summary: SQLite Export for YNAB - Export YNAB Data to SQLite
 Author-email: Max R <mxr@users.noreply.github.com>
 License-Expression: MIT
@@ -10,7 +10,7 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
-Requires-Python: >=3.12
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: aiohttp>=3
@@ -20,17 +20,20 @@ Requires-Dist: asyncio-for-ynab~=1.86.0
 Requires-Dist: fasteners
 Requires-Dist: rich>=10
 Requires-Dist: tenacity
+Requires-Dist: typing-extensions; python_version < "3.12"
 Dynamic: license-file
 
 # sqlite-export-for-ynab
 
-[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main) [![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
+[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main)
+[![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
 
 SQLite Export for YNAB - Export YNAB Budget Data to SQLite
 
 ## What This Does
 
-Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your data with any tools compatible with SQLite.
+Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your
+data with any tools compatible with SQLite.
 
 ## Installation
 
@@ -42,7 +45,8 @@ $ pip install sqlite-export-for-ynab
 
 ### CLI
 
-Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment variable.
+Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment
+variable.
 
 ```console
 $ export YNAB_PERSONAL_ACCESS_TOKEN="..."
@@ -54,17 +58,22 @@ Run the tool from the terminal to download your plans:
 $ sqlite-export-for-ynab
 ```
 
-Running it again will pull only data that changed since the last pull (this is done with [Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the `--full-refresh` flag.
-Pass `--quiet` to suppress all CLI output, including progress bars.
+Running it again will pull only data that changed since the last pull (this is done with
+[Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the
+`--full-refresh` flag. Pass `--quiet` to suppress all CLI output, including progress bars.
 
 <a id="db-path"></a>You can specify the DB path with the following options
+
 1. The `--db` flag.
-1. The `XDG_DATA_HOME` variable (see the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
-1. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
+2. The `XDG_DATA_HOME` variable (see the
+   [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that
+   case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
+3. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
 
 ### Library
 
-The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use them as follows:
+The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use
+them as follows:
 
 ```python
 import asyncio
@@ -82,11 +91,17 @@ asyncio.run(sync(token, db, full_refresh))
 
 ## Relations
 
-The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with [YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some additions:
+The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with
+[YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some
+additions:
 
-1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions, loan account periodic values).
-1. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
-1. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions` respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields to make querying more ergonomic.
+1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions,
+   loan account periodic values).
+2. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
+3. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and
+   non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions`
+   respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields
+   to make querying more ergonomic.
 
 ## Querying
 
@@ -96,10 +111,10 @@ You can issue queries with typical SQLite tools. *`sqlite-export-for-ynab` delib
 
 You can run the queries from this README using a tool like [`mdq`](https://github.com/yshavit/mdq). For example:
 
-```console
+````console
 $ mdq '```sql dupes' path/to/sqlite-export-for-ynab/README.md -o plain \
     | sqlite3 path/to/sqlite-export-for-ynab/db.sqlite
-```
+````
 
 The DB path is documented [above](#db-path).
 
@@ -233,7 +248,7 @@ FROM (
 ;
 ```
 
-To estimate taxable interest for a given year[^1]:
+To estimate taxable interest for a given year\[^1\]:
 
 ```sql
 -- Parameters expected by this query:
@@ -591,4 +606,6 @@ WHERE
 ;
 ```
 
-[^1]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified professional.
+\[^1\]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax
+advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified
+professional.

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/README.md

@@ -1,12 +1,14 @@
 # sqlite-export-for-ynab
 
-[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main) [![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
+[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main)
+[![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
 
 SQLite Export for YNAB - Export YNAB Budget Data to SQLite
 
 ## What This Does
 
-Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your data with any tools compatible with SQLite.
+Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your
+data with any tools compatible with SQLite.
 
 ## Installation
 
@@ -18,7 +20,8 @@ $ pip install sqlite-export-for-ynab
 
 ### CLI
 
-Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment variable.
+Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment
+variable.
 
 ```console
 $ export YNAB_PERSONAL_ACCESS_TOKEN="..."
@@ -30,17 +33,22 @@ Run the tool from the terminal to download your plans:
 $ sqlite-export-for-ynab
 ```
 
-Running it again will pull only data that changed since the last pull (this is done with [Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the `--full-refresh` flag.
-Pass `--quiet` to suppress all CLI output, including progress bars.
+Running it again will pull only data that changed since the last pull (this is done with
+[Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the
+`--full-refresh` flag. Pass `--quiet` to suppress all CLI output, including progress bars.
 
 <a id="db-path"></a>You can specify the DB path with the following options
+
 1. The `--db` flag.
-1. The `XDG_DATA_HOME` variable (see the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
-1. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
+2. The `XDG_DATA_HOME` variable (see the
+   [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that
+   case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
+3. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
 
 ### Library
 
-The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use them as follows:
+The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use
+them as follows:
 
 ```python
 import asyncio
@@ -58,11 +66,17 @@ asyncio.run(sync(token, db, full_refresh))
 
 ## Relations
 
-The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with [YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some additions:
+The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with
+[YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some
+additions:
 
-1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions, loan account periodic values).
-1. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
-1. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions` respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields to make querying more ergonomic.
+1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions,
+   loan account periodic values).
+2. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
+3. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and
+   non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions`
+   respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields
+   to make querying more ergonomic.
 
 ## Querying
 
@@ -72,10 +86,10 @@ You can issue queries with typical SQLite tools. *`sqlite-export-for-ynab` delib
 
 You can run the queries from this README using a tool like [`mdq`](https://github.com/yshavit/mdq). For example:
 
-```console
+````console
 $ mdq '```sql dupes' path/to/sqlite-export-for-ynab/README.md -o plain \
     | sqlite3 path/to/sqlite-export-for-ynab/db.sqlite
-```
+````
 
 The DB path is documented [above](#db-path).
 
@@ -209,7 +223,7 @@ FROM (
 ;
 ```
 
-To estimate taxable interest for a given year[^1]:
+To estimate taxable interest for a given year\[^1\]:
 
 ```sql
 -- Parameters expected by this query:
@@ -567,4 +581,6 @@ WHERE
 ;
 ```
 
-[^1]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified professional.
+\[^1\]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax
+advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified
+professional.

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/pyproject.toml

@@ -26,6 +26,7 @@ dependencies = [
   "fasteners",
   "rich>=10",
   "tenacity",
+  "typing-extensions; python_version<'3.12'",
 ]
 description = "SQLite Export for YNAB - Export YNAB Data to SQLite"
 keywords = ["ynab", "sqlite", "sql", "budget", "plan", "cli"]
@@ -33,8 +34,8 @@ license = "MIT"
 license-files = ["LICENSE"]
 name = "sqlite_export_for_ynab"
 readme = "README.md"
-requires-python = ">=3.12"
-version = "2.9.5"
+requires-python = ">=3.11"
+version = "2.9.7"
 
 [project.scripts]
 sqlite-export-for-ynab = "sqlite_export_for_ynab._main:main"
@@ -65,18 +66,23 @@ module = "tests.*"
 asyncio_default_fixture_loop_scope = "function"
 
 [tool.ruff]
-target-version = "py312"
+target-version = "py311"
 
 [tool.ruff.lint]
 extend-select = [
-  "UP",  # see pyupgrade
-  "B",  # see flake8-bugbear
   "A",  # see flake8-builtins
+  "B",  # see flake8-bugbear
   "C4",  # see flake8-comprehension
+  "I",  # sort imports
   "SIM",  # see flake8-simplify
   "TC",  # see flake8-type-checking
+  "UP",  # see pyupgrade
 ]
 
+[tool.ruff.lint.isort]
+force-single-line = true
+required-imports = ["from __future__ import annotations"]
+
 [tool.setuptools.package-data]
 sqlite_export_for_ynab = ["py.typed"]
 "sqlite_export_for_ynab.ddl" = ["*.sql"]

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/sqlite_export_for_ynab/_main.py

@@ -3,21 +3,24 @@ from __future__ import annotations
 import argparse
 import asyncio
 import os
+import sys
 from contextlib import asynccontextmanager
 from contextlib import contextmanager
 from dataclasses import dataclass
 from dataclasses import fields
 from datetime import date
+from datetime import datetime
 from datetime import timedelta
 from importlib import resources
 from importlib.metadata import version
-from itertools import batched
 from pathlib import Path
+from typing import TYPE_CHECKING
 from typing import Any
 from typing import Literal
+from typing import TypeVar
+from typing import cast
+from typing import get_args
 from typing import overload
-from typing import override
-from typing import TYPE_CHECKING
 
 import aiosqlite
 import asyncio_for_ynab  # noqa: F401
@@ -53,11 +56,30 @@ if TYPE_CHECKING:
     from collections.abc import AsyncIterator
     from collections.abc import Awaitable
     from collections.abc import Callable
+    from collections.abc import Iterable
     from collections.abc import Iterator
     from collections.abc import Sequence
 
+_T = TypeVar("_T")
+
+if sys.version_info >= (3, 12):  # pragma: >=3.12 cover
+    from itertools import batched
+    from typing import override
+else:  # pragma: <3.12 cover
+    from itertools import islice
+
+    from typing_extensions import override
+
+    def batched(iterable: Iterable[_T], n: int) -> Iterator[tuple[_T, ...]]:
+        it = iter(iterable)
+        while batch := tuple(islice(it, n)):
+            yield batch
+
+
 try:
-    from rich.progress import MofNCompleteColumn
+    from rich.progress import (
+        MofNCompleteColumn,  # pyright: ignore[reportAssignmentType]
+    )
 # https://github.com/benleb/surepy/issues/240
 except ImportError:  # pragma: no cover
     from rich.progress import ProgressColumn
@@ -84,28 +106,24 @@ except ImportError:  # pragma: no cover
             )
 
 
-_EntryTable = (
-    Literal["accounts"]
-    | Literal["account_periodic_values"]
-    | Literal["category_groups"]
-    | Literal["categories"]
-    | Literal["payees"]
-    | Literal["transactions"]
-    | Literal["subtransactions"]
-    | Literal["scheduled_transactions"]
-    | Literal["scheduled_subtransactions"]
-)
-_Endpoint = (
-    Literal["accounts"]
-    | Literal["categories"]
-    | Literal["payees"]
-    | Literal["transactions"]
-    | Literal["scheduled_transactions"]
-)
-_ENDPOINTS = tuple(lit.__args__[0] for lit in _Endpoint.__args__)
+_EntryTable = Literal[
+    "accounts",
+    "account_periodic_values",
+    "category_groups",
+    "categories",
+    "payees",
+    "transactions",
+    "subtransactions",
+    "scheduled_transactions",
+    "scheduled_subtransactions",
+]
+_Endpoint = Literal[
+    "accounts", "categories", "payees", "transactions", "scheduled_transactions"
+]
+_ENDPOINTS = get_args(_Endpoint)
 _ALL_RELATIONS = frozenset(
     ("plans", "flat_transactions", "scheduled_flat_transactions")
-    + tuple(lit.__args__[0] for lit in _EntryTable.__args__)
+    + get_args(_EntryTable)
 )
 
 _ENV_TOKEN = "YNAB_PERSONAL_ACCESS_TOKEN"
@@ -159,9 +177,9 @@ async def async_main(
     )
 
     args = parser.parse_args(argv)
-    db: Path = args.db
-    full_refresh: bool = args.full_refresh
-    quiet: bool = args.quiet
+    db = cast("Path", args.db)
+    full_refresh = cast("bool", args.full_refresh)
+    quiet = cast("bool", args.quiet)
 
     token = resolve_token(token_override)
 
@@ -556,28 +574,20 @@ async def insert_nested_entries(
     context: _Context,
     plan_id: str,
     entries: list[dict[str, Any]],
-    desc: (
-        Literal["Accounts"]
-        | Literal["Categories"]
-        | Literal["Transactions"]
-        | Literal["Scheduled Transactions"]
-    ),
+    desc: (Literal["Accounts", "Categories", "Transactions", "Scheduled Transactions"]),
     entries_name: (
-        Literal["accounts"]
-        | Literal["category_groups"]
-        | Literal["transactions"]
-        | Literal["scheduled_transactions"]
+        Literal["accounts", "category_groups", "transactions", "scheduled_transactions"]
     ),
     subentries_name: (
-        Literal["account_periodic_values"]
-        | Literal["categories"]
-        | Literal["subtransactions"]
+        Literal["account_periodic_values", "categories", "subtransactions"]
     ),
     subentries_table_name: (
-        Literal["account_periodic_values"]
-        | Literal["categories"]
-        | Literal["subtransactions"]
-        | Literal["scheduled_subtransactions"]
+        Literal[
+            "account_periodic_values",
+            "categories",
+            "subtransactions",
+            "scheduled_subtransactions",
+        ]
     ),
 ) -> None:
     if not entries:
@@ -684,7 +694,7 @@ class _ProgressYnab:
     task_id: TaskID
 
     @retry(stop=stop_after_attempt(3))
-    async def get[T](self, endpoint: Callable[..., Awaitable[T]]) -> T:
+    async def get(self, endpoint: Callable[..., Awaitable[_T]]) -> _T:
         try:
             return await endpoint(
                 plan_id=self.plan_id,
@@ -713,7 +723,7 @@ class ChunkedTransactionsApi:
     async def _get(
         self, transactions_api: TransactionsApi, plan_id: str
     ) -> TransactionsResponse:
-        today = date.today()
+        today = datetime.now().astimezone().date()
         responses = await asyncio.gather(
             *(
                 self._chunk(transactions_api, plan_id, sd, ud)

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7/sqlite_export_for_ynab.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlite_export_for_ynab
-Version: 2.9.5
+Version: 2.9.7
 Summary: SQLite Export for YNAB - Export YNAB Data to SQLite
 Author-email: Max R <mxr@users.noreply.github.com>
 License-Expression: MIT
@@ -10,7 +10,7 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
-Requires-Python: >=3.12
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: aiohttp>=3
@@ -20,17 +20,20 @@ Requires-Dist: asyncio-for-ynab~=1.86.0
 Requires-Dist: fasteners
 Requires-Dist: rich>=10
 Requires-Dist: tenacity
+Requires-Dist: typing-extensions; python_version < "3.12"
 Dynamic: license-file
 
 # sqlite-export-for-ynab
 
-[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main) [![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
+[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/mxr/sqlite-export-for-ynab/main.svg)](https://results.pre-commit.ci/latest/github/mxr/sqlite-export-for-ynab/main)
+[![codecov](https://codecov.io/github/mxr/sqlite-export-for-ynab/graph/badge.svg?token=NVCP6RDKSH)](https://codecov.io/github/mxr/sqlite-export-for-ynab)
 
 SQLite Export for YNAB - Export YNAB Budget Data to SQLite
 
 ## What This Does
 
-Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your data with any tools compatible with SQLite.
+Export all your [YNAB](https://ynab.com/) plans to a local [SQLite](https://www.sqlite.org/) DB. Then you can query your
+data with any tools compatible with SQLite.
 
 ## Installation
 
@@ -42,7 +45,8 @@ $ pip install sqlite-export-for-ynab
 
 ### CLI
 
-Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment variable.
+Provision a [YNAB Personal Access Token](https://api.ynab.com/#personal-access-tokens) and save it as an environment
+variable.
 
 ```console
 $ export YNAB_PERSONAL_ACCESS_TOKEN="..."
@@ -54,17 +58,22 @@ Run the tool from the terminal to download your plans:
 $ sqlite-export-for-ynab
 ```
 
-Running it again will pull only data that changed since the last pull (this is done with [Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the `--full-refresh` flag.
-Pass `--quiet` to suppress all CLI output, including progress bars.
+Running it again will pull only data that changed since the last pull (this is done with
+[Delta Requests](https://api.ynab.com/#deltas)). If you want to wipe the DB and pull all data again use the
+`--full-refresh` flag. Pass `--quiet` to suppress all CLI output, including progress bars.
 
 <a id="db-path"></a>You can specify the DB path with the following options
+
 1. The `--db` flag.
-1. The `XDG_DATA_HOME` variable (see the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
-1. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
+2. The `XDG_DATA_HOME` variable (see the
+   [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html)). In that
+   case the DB is saved in `"${XDG_DATA_HOME}"/sqlite-export-for-ynab/db.sqlite`.
+3. If neither is set, the DB is saved in `~/.local/share/sqlite-export-for-ynab/db.sqlite`.
 
 ### Library
 
-The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use them as follows:
+The library exposes the package `sqlite_export_for_ynab` and two functions - `default_db_path` and `sync`. You can use
+them as follows:
 
 ```python
 import asyncio
@@ -82,11 +91,17 @@ asyncio.run(sync(token, db, full_refresh))
 
 ## Relations
 
-The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with [YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some additions:
+The relations are defined in [create-relations.sql](sqlite_export_for_ynab/ddl/create-relations.sql). They are 1:1 with
+[YNAB's OpenAPI Spec](https://api.ynab.com/papi/open_api_spec.yaml) (ex: transactions, accounts, etc) with some
+additions:
 
-1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions, loan account periodic values).
-1. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
-1. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions` respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields to make querying more ergonomic.
+1. Some objects are pulled out into their own tables so they can be more cleanly modeled in SQLite (ex: subtransactions,
+   loan account periodic values).
+2. Foreign keys are added as needed (ex: plan ID, transaction ID) so data across plans remains separate.
+3. Two new views called `flat_transactions` and `scheduled_flat_transactions`. These allow you to query split and
+   non-split transactions easily, without needing to also query `subtransactions` and `scheduled_subtransactions`
+   respectively. They also filter out deleted/unapproved transactions/subtransactions and project payee/category fields
+   to make querying more ergonomic.
 
 ## Querying
 
@@ -96,10 +111,10 @@ You can issue queries with typical SQLite tools. *`sqlite-export-for-ynab` delib
 
 You can run the queries from this README using a tool like [`mdq`](https://github.com/yshavit/mdq). For example:
 
-```console
+````console
 $ mdq '```sql dupes' path/to/sqlite-export-for-ynab/README.md -o plain \
     | sqlite3 path/to/sqlite-export-for-ynab/db.sqlite
-```
+````
 
 The DB path is documented [above](#db-path).
 
@@ -233,7 +248,7 @@ FROM (
 ;
 ```
 
-To estimate taxable interest for a given year[^1]:
+To estimate taxable interest for a given year\[^1\]:
 
 ```sql
 -- Parameters expected by this query:
@@ -591,4 +606,6 @@ WHERE
 ;
 ```
 
-[^1]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified professional.
+\[^1\]: This query is a rough estimate based on YNAB data and optional user inputs. It is not financial advice, tax
+advice, or a substitute for Forms 1099-INT, brokerage statements, bank records, or guidance from a qualified
+professional.

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/sqlite_export_for_ynab.egg-info/requires.txt

@@ -5,3 +5,6 @@ asyncio-for-ynab~=1.86.0
 fasteners
 rich>=10
 tenacity
+
+[:python_version < "3.12"]
+typing-extensions

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/testing/fixtures.py

@@ -29,7 +29,6 @@ from asyncio_for_ynab import TransactionDetail
 from asyncio_for_ynab import TransactionsResponse
 from asyncio_for_ynab import TransactionsResponseData
 
-
 PLAN_ID_1 = str(uuid4())
 PLAN_ID_2 = str(uuid4())
 

{sqlite_export_for_ynab-2.9.5 → sqlite_export_for_ynab-2.9.7}/tests/_main_test.py

@@ -15,16 +15,16 @@ from rich.progress import Progress
 
 from sqlite_export_for_ynab import default_db_path
 from sqlite_export_for_ynab._main import _ALL_RELATIONS
-from sqlite_export_for_ynab._main import _Context
-from sqlite_export_for_ynab._main import _context
 from sqlite_export_for_ynab._main import _ENV_TOKEN
-from sqlite_export_for_ynab._main import _get_plan_summaries
 from sqlite_export_for_ynab._main import _PACKAGE
 from sqlite_export_for_ynab._main import _PROGRESS_COLUMNS
+from sqlite_export_for_ynab._main import ChunkedTransactionsApi
+from sqlite_export_for_ynab._main import _Context
+from sqlite_export_for_ynab._main import _context
+from sqlite_export_for_ynab._main import _get_plan_summaries
 from sqlite_export_for_ynab._main import _quarterly
 from sqlite_export_for_ynab._main import async_main
 from sqlite_export_for_ynab._main import asyncio_for_ynab
-from sqlite_export_for_ynab._main import ChunkedTransactionsApi
 from sqlite_export_for_ynab._main import contents
 from sqlite_export_for_ynab._main import get_last_knowledge_of_server
 from sqlite_export_for_ynab._main import get_relations
@@ -41,8 +41,6 @@ from sqlite_export_for_ynab._main import sync
 from testing.fixtures import ACCOUNT_ID_1
 from testing.fixtures import ACCOUNT_ID_2
 from testing.fixtures import ACCOUNTS
-from testing.fixtures import accounts_response
-from testing.fixtures import categories_response
 from testing.fixtures import CATEGORY_GOAL_TARGET_DATE_1
 from testing.fixtures import CATEGORY_GROUP_ID_1
 from testing.fixtures import CATEGORY_GROUP_ID_2
@@ -61,10 +59,8 @@ from testing.fixtures import LKOS
 from testing.fixtures import PAYEE_ID_1
 from testing.fixtures import PAYEE_ID_2
 from testing.fixtures import PAYEES
-from testing.fixtures import payees_response
 from testing.fixtures import PLAN_ID_1
 from testing.fixtures import PLAN_ID_2
-from testing.fixtures import plan_response
 from testing.fixtures import PLANS
 from testing.fixtures import SCHEDULED_SUBTRANSACTION_ID_1
 from testing.fixtures import SCHEDULED_SUBTRANSACTION_ID_2
@@ -72,7 +68,6 @@ from testing.fixtures import SCHEDULED_TRANSACTION_ID_1
 from testing.fixtures import SCHEDULED_TRANSACTION_ID_2
 from testing.fixtures import SCHEDULED_TRANSACTION_ID_3
 from testing.fixtures import SCHEDULED_TRANSACTIONS
-from testing.fixtures import scheduled_transactions_response
 from testing.fixtures import SERVER_KNOWLEDGE_1
 from testing.fixtures import SERVER_KNOWLEDGE_2
 from testing.fixtures import SUBTRANSACTION_ID_1
@@ -83,6 +78,11 @@ from testing.fixtures import TRANSACTION_ID_1
 from testing.fixtures import TRANSACTION_ID_2
 from testing.fixtures import TRANSACTION_ID_3
 from testing.fixtures import TRANSACTIONS
+from testing.fixtures import accounts_response
+from testing.fixtures import categories_response
+from testing.fixtures import payees_response
+from testing.fixtures import plan_response
+from testing.fixtures import scheduled_transactions_response
 from testing.fixtures import transactions_response