evernote2unbent 0.1.0__tar.gz

evernote2unbent-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,61 @@
+name: Publish
+
+# Publishing is driven by tags, so a release is `git tag v0.1.0 && git push --tags`
+# rather than a checklist someone has to remember at the end of a long day.
+on:
+  push:
+    tags: ["v*"]
+  # Manual runs go to TestPyPI, so the publishing path itself can be exercised without
+  # burning a real version number — PyPI refuses to reuse one, even after a delete.
+  workflow_dispatch:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install ${{ matrix.python-version }}
+      - run: uv sync --group test --group dev
+      - run: uv run ruff check src tests
+      - run: uv run ruff format --check src tests
+      - run: uv run pytest tests/ -q
+
+  publish:
+    # Gated on the tests: a tag that fails them should not become a release anyone can
+    # install, and PyPI versions cannot be replaced once published.
+    needs: test
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      # Trusted Publishing: PyPI verifies this workflow's identity through OIDC, so there
+      # is no API token to store, rotate, or leak.
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+
+      - name: Check the tag matches the version in pyproject.toml
+        if: startsWith(github.ref, 'refs/tags/')
+        run: |
+          TAG="${GITHUB_REF#refs/tags/v}"
+          VERSION=$(uv run python -c "import tomllib,pathlib;print(tomllib.loads(pathlib.Path('pyproject.toml').read_text())['project']['version'])")
+          if [ "$TAG" != "$VERSION" ]; then
+            echo "Tag v$TAG does not match pyproject version $VERSION." >&2
+            echo "Bump the version, commit, then tag." >&2
+            exit 1
+          fi
+
+      - name: Publish to TestPyPI
+        if: github.event_name == 'workflow_dispatch'
+        run: uv publish --publish-url https://test.pypi.org/legacy/
+
+      - name: Publish to PyPI
+        if: startsWith(github.ref, 'refs/tags/')
+        run: uv publish

evernote2unbent-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,26 @@
+name: Test
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        # The three platforms people migrate on. Windows is included because the token
+        # and config stores touch file modes, which behave differently there.
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python-version: ["3.10", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv python install ${{ matrix.python-version }}
+      - run: uv sync --group test --group dev
+      - run: uv run ruff check src tests
+      - run: uv run pytest tests/ -q

evernote2unbent-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+# Local Evernote sync database — data, routinely gigabytes.
+en_backup.db
+*.db
+
+.venv/
+dist/
+__pycache__/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/

evernote2unbent-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 C Deutsch
+
+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.

evernote2unbent-0.1.0/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.5
+Name: evernote2unbent
+Version: 0.1.0
+Summary: Move your Evernote notes into Unbent, without an ENEX file in between.
+Project-URL: Homepage, https://github.com/cdeutsch/evernote2unbent
+Project-URL: Unbent, https://unbent.app
+Project-URL: evernote-backup, https://github.com/vzhd1701/evernote-backup
+Author: C Deutsch
+License: MIT
+License-File: LICENSE
+Keywords: enex,evernote,export,migration,notes,unbent
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1
+Requires-Dist: evernote-backup>=1.14.0
+Requires-Dist: requests>=2.31
+Description-Content-Type: text/markdown
+
+# evernote2unbent
+
+Move your Evernote notes into [Unbent](https://unbent.app) — notes, notebooks, tags and
+attachments — without exporting an ENEX file first.
+
+Evernote has no export API, so every other route runs through the desktop client's
+File → Export, which is manual, unreliable past a few thousand notes, and produces
+multi-gigabyte files you then have to feed somewhere. This syncs your account with
+[evernote-backup](https://github.com/vzhd1701/evernote-backup) and uploads straight from
+its local database.
+
+## Install
+
+```bash
+uv tool install evernote2unbent
+```
+
+Or with pipx:
+
+```bash
+pipx install evernote2unbent
+```
+
+## Use
+
+```bash
+evernote2unbent migrate
+```
+
+That signs you in to Evernote, syncs your account to a local database, then uploads
+everything to Unbent. It asks which Unbent instance to use the first time and remembers
+the answer.
+
+**Start with one notebook** to see the result before moving everything. The sync still
+fetches your whole account — it is the upload that is scoped:
+
+```bash
+evernote2unbent migrate -n "Some Notebook"
+```
+
+Interrupted runs are safe to repeat: the sync is incremental, and notes that already
+landed are skipped rather than duplicated.
+
+### Doing the steps separately
+
+`migrate` runs [evernote-backup](https://github.com/vzhd1701/evernote-backup) for you. If
+you already use it, or want the ENEX files too, run the halves yourself:
+
+```bash
+evernote-backup init-db
+evernote-backup sync
+evernote2unbent upload
+```
+
+## Re-running is safe
+
+Unbent keys each note on a hash of its title and body, so a note that already landed is
+skipped rather than duplicated. That makes an interrupted upload resumable by simply
+repeating the command — and a note whose attachments failed partway gets only the missing
+files on the next run.
+
+Nothing here deletes or modifies anything in Evernote.
+
+## Options
+
+| Flag | Meaning |
+| --- | --- |
+| `-d, --database` | The database `evernote-backup sync` wrote (default `en_backup.db`) |
+| `-n, --notebook` | Only this notebook. Repeatable |
+| `-t, --tag` | Only notes with this tag. Repeatable |
+| `--include-trash` | Include notes from Evernote's trash |
+| `--url` | Instance for one command, without storing it |
+
+## Signing in
+
+`login` prints a short code and a link. Approving it in a browser you are already signed in
+to grants an ordinary session — no password is typed into the terminal, and no long-lived
+key is pasted from a settings page.
+
+The token is stored in `~/.config/unbent/credentials.json` at mode `0600`, keyed by
+instance so a token for one server is never sent to another. `logout` forgets it locally;
+signing out everywhere in Unbent revokes it for real.
+
+## Which instance
+
+There is deliberately no default. A guessed instance means a forgotten flag can send a
+migration to a server you did not choose, and that failure is silent, because uploading to
+the wrong Unbent still succeeds.
+
+The answer is stored in `~/.config/unbent/config.json` — plain JSON, mode `0644`, separate
+from the credentials file so changing a URL never means opening one with a token in it.
+
+```bash
+evernote2unbent set-url https://unbent.app
+evernote2unbent show-config
+```
+
+`$UNBENT_URL` overrides it for a shell session, `--url` for a single command.
+
+## What gets converted
+
+Notes arrive as Markdown. The conversion happens server-side in Unbent, which is why this
+package does not implement one: Unbent's own importer already has a tested ENML converter,
+and a second implementation here would drift from it.
+
+Attachments upload separately as raw bytes and are linked from the note body by their
+content hash, which is how an inline image ends up in the right place.
+
+## Credit
+
+The hard part — Evernote authentication, the Thrift API client, and incremental sync — is
+[evernote-backup](https://github.com/vzhd1701/evernote-backup) by
+[vzhd1701](https://github.com/vzhd1701), used here as a dependency rather than forked. This
+package adds an uploader and a CLI on top of it and modifies none of it.
+
+If you want ENEX files rather than a migration, use evernote-backup directly; it does that
+well and this is not a replacement for it.
+
+## License
+
+MIT

evernote2unbent-0.1.0/README.md

@@ -0,0 +1,121 @@
+# evernote2unbent
+
+Move your Evernote notes into [Unbent](https://unbent.app) — notes, notebooks, tags and
+attachments — without exporting an ENEX file first.
+
+Evernote has no export API, so every other route runs through the desktop client's
+File → Export, which is manual, unreliable past a few thousand notes, and produces
+multi-gigabyte files you then have to feed somewhere. This syncs your account with
+[evernote-backup](https://github.com/vzhd1701/evernote-backup) and uploads straight from
+its local database.
+
+## Install
+
+```bash
+uv tool install evernote2unbent
+```
+
+Or with pipx:
+
+```bash
+pipx install evernote2unbent
+```
+
+## Use
+
+```bash
+evernote2unbent migrate
+```
+
+That signs you in to Evernote, syncs your account to a local database, then uploads
+everything to Unbent. It asks which Unbent instance to use the first time and remembers
+the answer.
+
+**Start with one notebook** to see the result before moving everything. The sync still
+fetches your whole account — it is the upload that is scoped:
+
+```bash
+evernote2unbent migrate -n "Some Notebook"
+```
+
+Interrupted runs are safe to repeat: the sync is incremental, and notes that already
+landed are skipped rather than duplicated.
+
+### Doing the steps separately
+
+`migrate` runs [evernote-backup](https://github.com/vzhd1701/evernote-backup) for you. If
+you already use it, or want the ENEX files too, run the halves yourself:
+
+```bash
+evernote-backup init-db
+evernote-backup sync
+evernote2unbent upload
+```
+
+## Re-running is safe
+
+Unbent keys each note on a hash of its title and body, so a note that already landed is
+skipped rather than duplicated. That makes an interrupted upload resumable by simply
+repeating the command — and a note whose attachments failed partway gets only the missing
+files on the next run.
+
+Nothing here deletes or modifies anything in Evernote.
+
+## Options
+
+| Flag | Meaning |
+| --- | --- |
+| `-d, --database` | The database `evernote-backup sync` wrote (default `en_backup.db`) |
+| `-n, --notebook` | Only this notebook. Repeatable |
+| `-t, --tag` | Only notes with this tag. Repeatable |
+| `--include-trash` | Include notes from Evernote's trash |
+| `--url` | Instance for one command, without storing it |
+
+## Signing in
+
+`login` prints a short code and a link. Approving it in a browser you are already signed in
+to grants an ordinary session — no password is typed into the terminal, and no long-lived
+key is pasted from a settings page.
+
+The token is stored in `~/.config/unbent/credentials.json` at mode `0600`, keyed by
+instance so a token for one server is never sent to another. `logout` forgets it locally;
+signing out everywhere in Unbent revokes it for real.
+
+## Which instance
+
+There is deliberately no default. A guessed instance means a forgotten flag can send a
+migration to a server you did not choose, and that failure is silent, because uploading to
+the wrong Unbent still succeeds.
+
+The answer is stored in `~/.config/unbent/config.json` — plain JSON, mode `0644`, separate
+from the credentials file so changing a URL never means opening one with a token in it.
+
+```bash
+evernote2unbent set-url https://unbent.app
+evernote2unbent show-config
+```
+
+`$UNBENT_URL` overrides it for a shell session, `--url` for a single command.
+
+## What gets converted
+
+Notes arrive as Markdown. The conversion happens server-side in Unbent, which is why this
+package does not implement one: Unbent's own importer already has a tested ENML converter,
+and a second implementation here would drift from it.
+
+Attachments upload separately as raw bytes and are linked from the note body by their
+content hash, which is how an inline image ends up in the right place.
+
+## Credit
+
+The hard part — Evernote authentication, the Thrift API client, and incremental sync — is
+[evernote-backup](https://github.com/vzhd1701/evernote-backup) by
+[vzhd1701](https://github.com/vzhd1701), used here as a dependency rather than forked. This
+package adds an uploader and a CLI on top of it and modifies none of it.
+
+If you want ENEX files rather than a migration, use evernote-backup directly; it does that
+well and this is not a replacement for it.
+
+## License
+
+MIT

evernote2unbent-0.1.0/pyproject.toml

@@ -0,0 +1,56 @@
+[project]
+name = "evernote2unbent"
+version = "0.1.0"
+description = "Move your Evernote notes into Unbent, without an ENEX file in between."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [{ name = "C Deutsch" }]
+keywords = ["evernote", "unbent", "enex", "migration", "export", "notes"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: End Users/Desktop",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Topic :: Utilities",
+]
+
+dependencies = [
+    # The Evernote sync — account auth, incremental sync, and the local SQLite database
+    # this reads from. Depended on rather than forked: this package adds an uploader and a
+    # CLI and modifies none of it, so upstream fixes arrive with a version bump.
+    "evernote-backup>=1.14.0",
+    "click>=8.1",
+    "requests>=2.31",
+]
+
+[project.urls]
+Homepage = "https://github.com/cdeutsch/evernote2unbent"
+Unbent = "https://unbent.app"
+"evernote-backup" = "https://github.com/vzhd1701/evernote-backup"
+
+[project.scripts]
+evernote2unbent = "evernote2unbent.cli:main"
+
+[dependency-groups]
+test = ["pytest", "pytest-mock", "requests-mock"]
+dev = ["ruff", "ty"]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/evernote2unbent"]
+
+[tool.ruff]
+# 90, matching evernote-backup, whose prose comments this code was written alongside.
+line-length = 90
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM", "RUF"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/*.py" = ["S", "PL"]

evernote2unbent-0.1.0/src/evernote2unbent/__init__.py

@@ -0,0 +1,3 @@
+"""Move Evernote notes into Unbent, without an ENEX file in between."""
+
+__version__ = "0.1.0"