lzstring-codec 0.1.0__tar.gz

lzstring_codec-0.1.0/LICENSE

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

lzstring_codec-0.1.0/PKG-INFO

@@ -0,0 +1,202 @@
+Metadata-Version: 2.4
+Name: lzstring-codec
+Version: 0.1.0
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Rust
+Classifier: Topic :: System :: Archiving :: Compression
+Classifier: Typing :: Typed
+Requires-Dist: pytest>=8 ; extra == 'dev'
+Requires-Dist: ruff>=0.6 ; extra == 'dev'
+Provides-Extra: dev
+License-File: LICENSE
+License-File: THIRD_PARTY.md
+Summary: lz-string for Python, held byte-for-byte to the JavaScript original
+Keywords: lz-string,lzstring,lzstring-codec,compression,lzw,savegame,utf-16
+Author-email: Andrew Grinevich <beulea@gmail.com>
+License-Expression: MIT
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Homepage, https://github.com/Derfirm/lz-string
+Project-URL: Issues, https://github.com/Derfirm/lz-string/issues
+Project-URL: Source, https://github.com/Derfirm/lz-string
+Project-URL: Specification, https://github.com/Derfirm/lz-string/blob/master/SPEC.md
+
+# lzstring-codec
+
+lz-string for Python, held byte-for-byte to the JavaScript original.
+
+Installed as `lzstring-codec`, imported as `lz_string`. The obvious name is not available:
+PyPI refuses it as too similar to `lzstring`, which is one of the two packages this exists
+to replace.
+
+It exists because the package that *is* on PyPI gets the format wrong in ways that quietly
+corrupt real save files. It was written for [saveeditor.online](https://saveeditor.online),
+which reads a few thousand lz-string saves a week and cannot afford to hand any of them back
+altered.
+
+```python
+import lz_string as lz
+
+lz.compress_to_base64('{"gold":9000}')          # 'N4Ig5g9gNgJiBcBOADKgvkA='
+lz.decompress_from_base64(_)                    # '{"gold":9000}'
+```
+
+## Why
+
+`lzstring` 1.0.4 on PyPI is a line-by-line transliteration of the JavaScript, and it
+inherits neither its speed nor its correctness. Measured against 1202 vectors produced by
+`lz-string` 1.5.0 on npm — the library the games themselves use:
+
+- **294 vectors compress to different bytes**, because it walks Python code points where
+  the format is defined over UTF-16 code units. In practice: an emoji in a player's name is
+  written truncated, and the game reads back `U+F600`, a private-use box. Every save with an
+  astral character is corrupted on write.
+- **`decompressFromUTF16` raises `TypeError` on every input.** It subtracts an integer from
+  a string. The function has never worked.
+- Decompression rebuilds a 65-entry alphabet table *per character* and reads the bit stream
+  one bit at a time: **22 seconds** for a 1.8 MB save, on the request path.
+
+This package is byte-identical to the reference on all 1202 vectors, in all four
+transports, in both directions, on both backends — and 15–45× faster.
+
+How far that was pushed, because "it round-trips" is not the same as "it is right":
+
+| check | scale | result |
+|---|---|---|
+| golden corpus vs. node | 1202 vectors x 4 transports x 2 directions x 2 backends | identical |
+| real production saves | 38 files up to 1.8 MB, decompress **and** recompress | identical |
+| differential fuzz vs. node | 5000 generated inputs x 4 transports x 2 backends | identical |
+| malformed-input fuzz | 16000 probes x 2 backends | agree with each other and with the reference; nothing raised |
+
+The last row is the one that found bugs — two of them in this package, both invisible to
+every check above it, and both now pinned by tests. SPEC.md §4 says what they were.
+
+And it is not the only one: `py-lzstring` 0.1.1, a separate port of the same reference,
+differs from it on **295 of the same 1202 vectors**, first on exactly the same astral
+character. Two independent Python ports, the same mistake in both.
+
+See [SPEC.md](SPEC.md) for the format itself and for the full divergence table.
+
+## Installing
+
+The package is a compiled extension; `pip install` builds it, and a Rust toolchain is
+required to do so.
+
+```bash
+uv add git+ssh://git@github.com/Derfirm/lz-string.git    # or, in a checkout:
+uv sync                                                  # builds the extension in place
+pip install .                                            # pip works too; maturin does the build
+```
+
+An import without the extension raises rather than falling back to something slower and
+subtly different.
+
+**Build it where it will run.** The binary is tied to the C library it was linked against:
+one built on Debian bookworm (glibc 2.36) will not load on bullseye (2.31), which is what
+`python:3.12.11-slim-bullseye` — the image this package is destined for — is built on. It
+fails at import with `GLIBC_2.34 not found`, not at build time. Either build inside the
+target image, or produce a manylinux wheel.
+
+On two real saves, best of three in one run:
+
+| | decompress | compress |
+|---|---|---|
+| **this package**, 259 KB → 975 K chars | **0.004 s** | **0.044 s** |
+| `lzstring` 1.0.4, the same | 1.199 s | 0.312 s |
+| **this package**, 1.8 MB → 13.4 M chars | **0.054 s** | **1.547 s** |
+| `lzstring` 1.0.4, the same | 8.581 s | 4.766 s |
+
+Both halves are ours, and the only Rust dependency is pyo3. The obvious alternative,
+the [`lz-str`](https://crates.io/crates/lz-str) crate, was the starting point and did not
+survive contact with damaged input: it answers the same thing for two failures the reference
+keeps apart, skips characters the reference reads as zero bits, and refuses a payload whose
+trailing padding character was trimmed. SPEC.md §7 has the measurements.
+
+A pure-Python implementation of the whole format lives in `src/lz_string/_reference.py`.
+It is the test suite's second opinion, not a fallback: nothing imports it at runtime.
+
+## Migrating from `lzstring`
+
+The camelCase API is provided as-is, so the change is one import line:
+
+```python
+-from lzstring import LZString
++from lz_string import LZString
+```
+
+Two behaviour changes to know about, both improvements, both in SPEC.md: saves containing
+astral characters stop being corrupted, and `decompressFromUTF16` starts working.
+
+## Tests
+
+```bash
+uv sync --extra dev                      # .python-version pins 3.12, as in production
+uv run pytest                            # every test runs against both implementations
+uv sync --reinstall-package lzstring-codec   # after touching the Rust: rebuild it
+./tools/check_linux.sh                   # built and run inside the target image (needs docker)
+./tools/check_linux.sh linux/amd64       # and on production's architecture, cross-compiled
+```
+
+The Linux run is not ceremony. It is done in `python:3.12.11-slim-bullseye` — the exact image
+this is destined for — and it has already caught two things a laptop cannot: a test that
+measured the machine rather than the code, and an extension that built cleanly and then
+refused to load because it wanted a newer glibc than the image has.
+
+251 tests: the golden corpus per category and transport, the documented behaviour on damaged
+input, seeded round-trips over random code units and surrogate halves, parity between the
+shipped extension and the Python reference — including a fuzz of malformed payloads, which
+is what pins the three corrections the crate underneath needed — and two tests that the
+extension really does let go of the interpreter while it works.
+
+To regenerate the corpus (deterministic — a diff means the reference moved):
+
+```bash
+npm --prefix tools install
+node tools/gen_vectors.mjs
+```
+
+`tools/bench.py` reproduces the numbers above.
+
+## Releasing
+
+By tag, not by merge. Most merges here are documentation and CI, and PyPI refuses a second
+upload of the same version — publishing on merge would mean either a version bump per commit
+or a release job that fails as a matter of course.
+
+```bash
+# bump `version` in pyproject.toml, note it in CHANGELOG.md, merge, then:
+git tag v0.1.0 && git push origin v0.1.0
+```
+
+The workflow builds wheels for linux and macOS on both architectures plus an sdist, checks
+that the tag and the version in pyproject.toml agree, and only then uploads.
+`workflow_dispatch` runs everything except the upload, which is how the pipeline is tested
+without releasing anything.
+
+The upload needs a credential, and there are two ways to give it one. Either works; the
+first stores nothing.
+
+**Trusted publishing.** On PyPI, add a pending publisher for the project name with owner
+`Derfirm`, repository `lz-string`, workflow `release.yml`, environment `pypi`. Nothing to
+configure here — with no `PYPI_API_TOKEN` secret set, the publish step already exchanges a
+short-lived OIDC token, which is what it tries today and what fails with "Trusted publishing
+exchange failure" until the publisher exists.
+
+**A token.** Create an environment named `pypi` in the repository settings, put an API token
+in it as `PYPI_API_TOKEN`, and re-run the publish job of the tagged release. Protection
+rules on that environment are where you add an approval step if you want one.
+
+## Provenance and licence
+
+MIT (`LICENSE`). Compression comes from the [`lz-str`](https://crates.io/crates/lz-str)
+crate and the bindings from [pyo3](https://pyo3.rs), both MIT/Apache-2.0; the decoder is a
+port of [pieroxy/lz-string](https://github.com/pieroxy/lz-string), MIT, which is also the
+reference every claim here is measured against. See `THIRD_PARTY.md`.
+
+No user data lives in this repository: every test input is generated, and the corpus is the
+reference implementation's own output.
+

lzstring_codec-0.1.0/README.md

@@ -0,0 +1,174 @@
+# lzstring-codec
+
+lz-string for Python, held byte-for-byte to the JavaScript original.
+
+Installed as `lzstring-codec`, imported as `lz_string`. The obvious name is not available:
+PyPI refuses it as too similar to `lzstring`, which is one of the two packages this exists
+to replace.
+
+It exists because the package that *is* on PyPI gets the format wrong in ways that quietly
+corrupt real save files. It was written for [saveeditor.online](https://saveeditor.online),
+which reads a few thousand lz-string saves a week and cannot afford to hand any of them back
+altered.
+
+```python
+import lz_string as lz
+
+lz.compress_to_base64('{"gold":9000}')          # 'N4Ig5g9gNgJiBcBOADKgvkA='
+lz.decompress_from_base64(_)                    # '{"gold":9000}'
+```
+
+## Why
+
+`lzstring` 1.0.4 on PyPI is a line-by-line transliteration of the JavaScript, and it
+inherits neither its speed nor its correctness. Measured against 1202 vectors produced by
+`lz-string` 1.5.0 on npm — the library the games themselves use:
+
+- **294 vectors compress to different bytes**, because it walks Python code points where
+  the format is defined over UTF-16 code units. In practice: an emoji in a player's name is
+  written truncated, and the game reads back `U+F600`, a private-use box. Every save with an
+  astral character is corrupted on write.
+- **`decompressFromUTF16` raises `TypeError` on every input.** It subtracts an integer from
+  a string. The function has never worked.
+- Decompression rebuilds a 65-entry alphabet table *per character* and reads the bit stream
+  one bit at a time: **22 seconds** for a 1.8 MB save, on the request path.
+
+This package is byte-identical to the reference on all 1202 vectors, in all four
+transports, in both directions, on both backends — and 15–45× faster.
+
+How far that was pushed, because "it round-trips" is not the same as "it is right":
+
+| check | scale | result |
+|---|---|---|
+| golden corpus vs. node | 1202 vectors x 4 transports x 2 directions x 2 backends | identical |
+| real production saves | 38 files up to 1.8 MB, decompress **and** recompress | identical |
+| differential fuzz vs. node | 5000 generated inputs x 4 transports x 2 backends | identical |
+| malformed-input fuzz | 16000 probes x 2 backends | agree with each other and with the reference; nothing raised |
+
+The last row is the one that found bugs — two of them in this package, both invisible to
+every check above it, and both now pinned by tests. SPEC.md §4 says what they were.
+
+And it is not the only one: `py-lzstring` 0.1.1, a separate port of the same reference,
+differs from it on **295 of the same 1202 vectors**, first on exactly the same astral
+character. Two independent Python ports, the same mistake in both.
+
+See [SPEC.md](SPEC.md) for the format itself and for the full divergence table.
+
+## Installing
+
+The package is a compiled extension; `pip install` builds it, and a Rust toolchain is
+required to do so.
+
+```bash
+uv add git+ssh://git@github.com/Derfirm/lz-string.git    # or, in a checkout:
+uv sync                                                  # builds the extension in place
+pip install .                                            # pip works too; maturin does the build
+```
+
+An import without the extension raises rather than falling back to something slower and
+subtly different.
+
+**Build it where it will run.** The binary is tied to the C library it was linked against:
+one built on Debian bookworm (glibc 2.36) will not load on bullseye (2.31), which is what
+`python:3.12.11-slim-bullseye` — the image this package is destined for — is built on. It
+fails at import with `GLIBC_2.34 not found`, not at build time. Either build inside the
+target image, or produce a manylinux wheel.
+
+On two real saves, best of three in one run:
+
+| | decompress | compress |
+|---|---|---|
+| **this package**, 259 KB → 975 K chars | **0.004 s** | **0.044 s** |
+| `lzstring` 1.0.4, the same | 1.199 s | 0.312 s |
+| **this package**, 1.8 MB → 13.4 M chars | **0.054 s** | **1.547 s** |
+| `lzstring` 1.0.4, the same | 8.581 s | 4.766 s |
+
+Both halves are ours, and the only Rust dependency is pyo3. The obvious alternative,
+the [`lz-str`](https://crates.io/crates/lz-str) crate, was the starting point and did not
+survive contact with damaged input: it answers the same thing for two failures the reference
+keeps apart, skips characters the reference reads as zero bits, and refuses a payload whose
+trailing padding character was trimmed. SPEC.md §7 has the measurements.
+
+A pure-Python implementation of the whole format lives in `src/lz_string/_reference.py`.
+It is the test suite's second opinion, not a fallback: nothing imports it at runtime.
+
+## Migrating from `lzstring`
+
+The camelCase API is provided as-is, so the change is one import line:
+
+```python
+-from lzstring import LZString
++from lz_string import LZString
+```
+
+Two behaviour changes to know about, both improvements, both in SPEC.md: saves containing
+astral characters stop being corrupted, and `decompressFromUTF16` starts working.
+
+## Tests
+
+```bash
+uv sync --extra dev                      # .python-version pins 3.12, as in production
+uv run pytest                            # every test runs against both implementations
+uv sync --reinstall-package lzstring-codec   # after touching the Rust: rebuild it
+./tools/check_linux.sh                   # built and run inside the target image (needs docker)
+./tools/check_linux.sh linux/amd64       # and on production's architecture, cross-compiled
+```
+
+The Linux run is not ceremony. It is done in `python:3.12.11-slim-bullseye` — the exact image
+this is destined for — and it has already caught two things a laptop cannot: a test that
+measured the machine rather than the code, and an extension that built cleanly and then
+refused to load because it wanted a newer glibc than the image has.
+
+251 tests: the golden corpus per category and transport, the documented behaviour on damaged
+input, seeded round-trips over random code units and surrogate halves, parity between the
+shipped extension and the Python reference — including a fuzz of malformed payloads, which
+is what pins the three corrections the crate underneath needed — and two tests that the
+extension really does let go of the interpreter while it works.
+
+To regenerate the corpus (deterministic — a diff means the reference moved):
+
+```bash
+npm --prefix tools install
+node tools/gen_vectors.mjs
+```
+
+`tools/bench.py` reproduces the numbers above.
+
+## Releasing
+
+By tag, not by merge. Most merges here are documentation and CI, and PyPI refuses a second
+upload of the same version — publishing on merge would mean either a version bump per commit
+or a release job that fails as a matter of course.
+
+```bash
+# bump `version` in pyproject.toml, note it in CHANGELOG.md, merge, then:
+git tag v0.1.0 && git push origin v0.1.0
+```
+
+The workflow builds wheels for linux and macOS on both architectures plus an sdist, checks
+that the tag and the version in pyproject.toml agree, and only then uploads.
+`workflow_dispatch` runs everything except the upload, which is how the pipeline is tested
+without releasing anything.
+
+The upload needs a credential, and there are two ways to give it one. Either works; the
+first stores nothing.
+
+**Trusted publishing.** On PyPI, add a pending publisher for the project name with owner
+`Derfirm`, repository `lz-string`, workflow `release.yml`, environment `pypi`. Nothing to
+configure here — with no `PYPI_API_TOKEN` secret set, the publish step already exchanges a
+short-lived OIDC token, which is what it tries today and what fails with "Trusted publishing
+exchange failure" until the publisher exists.
+
+**A token.** Create an environment named `pypi` in the repository settings, put an API token
+in it as `PYPI_API_TOKEN`, and re-run the publish job of the tagged release. Protection
+rules on that environment are where you add an approval step if you want one.
+
+## Provenance and licence
+
+MIT (`LICENSE`). Compression comes from the [`lz-str`](https://crates.io/crates/lz-str)
+crate and the bindings from [pyo3](https://pyo3.rs), both MIT/Apache-2.0; the decoder is a
+port of [pieroxy/lz-string](https://github.com/pieroxy/lz-string), MIT, which is also the
+reference every claim here is measured against. See `THIRD_PARTY.md`.
+
+No user data lives in this repository: every test input is generated, and the corpus is the
+reference implementation's own output.

lzstring_codec-0.1.0/THIRD_PARTY.md

@@ -0,0 +1,23 @@
+# Third-party notices
+
+The Python and Rust code in this repository is MIT, see `LICENSE`. The compiled extension
+links one crate, and its notice is reproduced as its licence requires.
+
+## pyo3
+
+<https://crates.io/crates/pyo3> — MIT OR Apache-2.0. The Python bindings.
+
+## lz-string (JavaScript)
+
+<https://github.com/pieroxy/lz-string> — MIT, by Pieroxy. Not linked or redistributed: it is
+the *reference*. Both halves of the codec here are ports of it, its behaviour is what this
+package is measured against, and the golden vectors in `tests/data/vectors.jsonl.gz` are its
+output, produced by `tools/gen_vectors.mjs`. Everything this package claims about correctness
+is a claim about agreeing with it.
+
+## lz-str (Rust) — no longer a dependency
+
+<https://crates.io/crates/lz-str> — MIT OR Apache-2.0. This package wrapped it until its
+decompressor turned out to disagree with the reference on damaged input in three ways
+(SPEC.md §7). Nothing of it ships here now; the note is kept because the analysis in SPEC.md
+refers to it.

lzstring_codec-0.1.0/pyproject.toml

@@ -0,0 +1,55 @@
+[build-system]
+# 1.9 is the floor, not a guess: PEP 639 `license` / `license-files` below it are a
+# parse error, and the build fails with "wanted string or table".
+requires = ["maturin>=1.9,<2"]
+build-backend = "maturin"
+
+[project]
+name = "lzstring-codec"
+version = "0.1.0"
+description = "lz-string for Python, held byte-for-byte to the JavaScript original"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE", "THIRD_PARTY.md"]
+requires-python = ">=3.12"
+authors = [{ name = "Andrew Grinevich", email = "beulea@gmail.com" }]
+keywords = ["lz-string", "lzstring", "lzstring-codec", "compression", "lzw", "savegame", "utf-16"]
+dependencies = []
+
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Rust",
+    "Topic :: System :: Archiving :: Compression",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Homepage = "https://github.com/Derfirm/lz-string"
+Source = "https://github.com/Derfirm/lz-string"
+Issues = "https://github.com/Derfirm/lz-string/issues"
+Specification = "https://github.com/Derfirm/lz-string/blob/master/SPEC.md"
+
+[project.optional-dependencies]
+dev = ["pytest>=8", "ruff>=0.6"]
+
+# A mixed layout: Python under src/, the crate under rust/. maturin builds the extension
+# straight into the package, so `pip install` yields something that works rather than half
+# of something that does.
+[tool.maturin]
+python-source = "src"
+module-name = "lz_string._native"
+manifest-path = "rust/Cargo.toml"
+features = ["pyo3/extension-module"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["src", "."]
+addopts = "-q"
+
+[tool.ruff]
+line-length = 110
+target-version = "py312"

lzstring_codec-0.1.0/rust/Cargo.lock

@@ -0,0 +1,132 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 4
+
+[[package]]
+name = "heck"
+version = "0.5.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2304e00983f87ffb38b55b444b5e3b60a884b5d30c0fca7d82fe33449bbe55ea"
+
+[[package]]
+name = "libc"
+version = "0.2.189"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3eaf3ede3fee6db1a4c2ee091bf8a8b4dccdc6d17f656fb07896ee72867612f2"
+
+[[package]]
+name = "lz-string-native"
+version = "0.1.0"
+dependencies = [
+ "pyo3",
+]
+
+[[package]]
+name = "once_cell"
+version = "1.21.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9f7c3e4beb33f85d45ae3e3a1792185706c8e16d043238c593331cc7cd313b50"
+
+[[package]]
+name = "portable-atomic"
+version = "1.15.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "05c8b63e8d9609db387f0324918f81d68fe27748f084ef092fb35954d0539a85"
+
+[[package]]
+name = "proc-macro2"
+version = "1.0.107"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "985e7ec9bb745e6ce6535b544d84d6cd6f7ad8bd711c398938ae983b91a766d9"
+dependencies = [
+ "unicode-ident",
+]
+
+[[package]]
+name = "pyo3"
+version = "0.29.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4688ddedf473e32662b9b067670129a8afb8c18e351482c70d62ba4a88171e8b"
+dependencies = [
+ "libc",
+ "once_cell",
+ "portable-atomic",
+ "pyo3-build-config",
+ "pyo3-ffi",
+ "pyo3-macros",
+]
+
+[[package]]
+name = "pyo3-build-config"
+version = "0.29.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f41027e41b4bd03f6e60f9f417fe24a6341a6bb744edd62b6f709f2a52ea30e9"
+dependencies = [
+ "target-lexicon",
+]
+
+[[package]]
+name = "pyo3-ffi"
+version = "0.29.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e591a95526fead067432c3b3a33fc74770b87b1e04e73671090d9c2055a2b327"
+dependencies = [
+ "libc",
+ "pyo3-build-config",
+]
+
+[[package]]
+name = "pyo3-macros"
+version = "0.29.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "73225868fc1cd84eef2c3c230ddb91273bf1de46aeb8a4248da76d32a0924a1c"
+dependencies = [
+ "proc-macro2",
+ "pyo3-macros-backend",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "pyo3-macros-backend"
+version = "0.29.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "571575aa3749fa6216757dd47d2a3e7ef360f329a40f0666a9fbd14889024952"
+dependencies = [
+ "heck",
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "quote"
+version = "1.0.47"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1fbf4db142a473a8d80c26bbf18454ed458bf8d26c8219c331daecfdbd079001"
+dependencies = [
+ "proc-macro2",
+]
+
+[[package]]
+name = "syn"
+version = "2.0.119"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "872831b642d1a07999a962a351ed35b955ea2cfc8f3862091e2a240a84f17297"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "unicode-ident",
+]
+
+[[package]]
+name = "target-lexicon"
+version = "0.13.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "adb6935a6f5c20170eeceb1a3835a49e12e19d792f6dd344ccc76a985ca5a6ca"
+
+[[package]]
+name = "unicode-ident"
+version = "1.0.24"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e6e4313cd5fcd3dad5cafa179702e2b244f760991f45397d14d4ebf38247da75"

lzstring_codec-0.1.0/rust/Cargo.toml

@@ -0,0 +1,16 @@
+[package]
+name = "lz-string-native"
+version = "0.1.0"
+edition = "2021"
+publish = false
+
+[lib]
+name = "_native"
+crate-type = ["cdylib"]
+
+[dependencies]
+pyo3 = { version = "0.29", features = ["extension-module", "abi3-py312"] }
+
+[profile.release]
+opt-level = 3
+lto = true