{
  "generator": {
    "matra": "0.3.0",
    "udpipe_model": {
      "name": "english-ewt-ud-2.5-191206",
      "sha256": "784bd0fa85e3d831fd02a55290d0acfd05c953159dc38cc33d52e1b28add9957"
    }
  },
  "page": "explanation/install-routes.md",
  "paragraphs": [
    {
      "compression_ratio": 0.5725,
      "kind": "paragraph",
      "lexical_density": 0.5147,
      "readability_grade": 6.8934,
      "sentences": 4,
      "text": "matra is one Rust core published three ways: a library on crates.io, a command-line binary built from the same crate, and a Python package on PyPI. The routes differ in what they compile and what they print about themselves, and not in what an analysis returns. This page explains why the install commands look as they do. Install matra has the steps and Platforms and models the facts.",
      "words": 69
    },
    {
      "compression_ratio": 0.506,
      "kind": "paragraph",
      "lexical_density": 0.52,
      "readability_grade": 6.364,
      "sentences": 4,
      "text": "The matra command the Python package installs is not a Python program. From 0.2.0 it is the Rust command line, compiled into the library and reached through the extension module, so pip install and cargo install give you the same program with two launchers. 0.1.0 had a second command line written in Python, with a --json shape of its own and a model directory hardcoded to the pre-0.2.0 location. Two implementations of one interface drifted apart, which is why the command line now lives in the library: a binary target cannot be reached from Python, and a library module can.",
      "words": 101
    },
    {
      "compression_ratio": 0.5229,
      "kind": "paragraph",
      "lexical_density": 0.4875,
      "readability_grade": 4.2675,
      "sentences": 5,
      "text": "An unpinned install line takes whatever the registry hands out. Today that is 0.3.x on both registries, and it will not stay that way. 0.1.0 is also still published, and its matra is the separate Python implementation above. So is 0.2, whose surface 0.3.0 renamed throughout. The failure an unpinned line risks is not an error: the install succeeds and gives you a program these pages do not describe, so its version banner and its output do not match theirs.",
      "words": 81
    },
    {
      "compression_ratio": 0.5599,
      "kind": "paragraph",
      "lexical_density": 0.5125,
      "readability_grade": 2.42,
      "sentences": 3,
      "text": "The Python lines take a floor, 'matra>=0.3', because what they claim holds for 0.3.0 and every release after it, and an exact pin would still name 0.3.0 after a later release ships. The cargo lines take a caret requirement, matra@0.3 and --version '^0.3', which is how cargo states a version. Cargo reads a change in the first non-zero component as breaking, so the caret accepts 0.3.0 and later 0.3 releases and stops short of 0.4.0, which a floor would not.",
      "words": 81
    },
    {
      "compression_ratio": 0.5503,
      "kind": "paragraph",
      "lexical_density": 0.5625,
      "readability_grade": 8.94,
      "sentences": 5,
      "text": "The two banners differ, and both are correct. The CLI binary from cargo install is built with the features the command line needs, udpipe and cli. The wheel is built with python and model2vec on top, because the Python package also carries the library, embedding included. matra --version prints the version and then the features of the build that is running, so a report quoting it says which build produced a result. Every analysis command behaves the same in both.",
      "words": 80
    },
    {
      "compression_ratio": 0.5586,
      "kind": "paragraph",
      "lexical_density": 0.5738,
      "readability_grade": 7.7673,
      "sentences": 3,
      "text": "Free-threaded CPython is the one interpreter the wheels do not reach, and the reason is a tag, not a platform. The wheels are built once per platform against the CPython stable ABI and tagged abi3, which every GIL-enabled CPython from 3.12 accepts. A free-threaded interpreter accepts abi3t instead, so it falls back to building from source even where a wheel exists.",
      "words": 64
    },
    {
      "compression_ratio": 0.5397,
      "kind": "paragraph",
      "lexical_density": 0.4943,
      "readability_grade": 12.8097,
      "sentences": 3,
      "text": "The first call that needs the parsing model downloads it, about 16 MB from a university server, and that can take from a few seconds to over half a minute. The command line says so on stderr before it starts, because a blank terminal for that long is indistinguishable from a hung process. The library says nothing, because a program embedding matra chooses its own reporting: the constructors that take a notice callback hand it the same facts, and the program decides what to do with them.",
      "words": 87
    }
  ]
}
