elva-cli 0.0.2__tar.gz → 0.0.3__tar.gz

elva_cli-0.0.3/PKG-INFO

@@ -0,0 +1,95 @@
+Metadata-Version: 2.5
+Name: elva-cli
+Version: 0.0.3
+Summary: Elva - CLI for Theneo Elva
+Project-URL: Homepage, https://getelva.ai
+Project-URL: Source, https://github.com/Theneo-Inc/theneo-elva-cli
+Project-URL: Issues, https://github.com/Theneo-Inc/theneo-elva-cli/issues
+Author-email: Theneo <support@theneo.io>
+Keywords: api,cli,documentation,elva,openapi,theneo
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: typer<1.0,>=0.15
+Provides-Extra: dev
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pytest>=8.2; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Elva CLI
+
+Manage your [Elva](https://getelva.ai) API projects from the terminal: import specs,
+inspect collections, and generate MCP servers without opening a browser.
+
+> **Early alpha.** The command surface is still taking shape. This release ships
+> `--version` and `--help` only; the first working commands land in `0.1.0`.
+
+## Install
+
+Requires Python 3.11 or newer.
+
+```bash
+uv tool install elva-cli
+```
+
+Or with [pipx](https://pipx.pypa.io/), if you already use it:
+
+```bash
+pipx install elva-cli
+```
+
+Either way, `elva` is then available from any directory:
+
+```bash
+elva --version
+elva --help
+```
+
+To try it without installing anything:
+
+```bash
+uvx --from elva-cli elva --version
+```
+
+Don't have `uv`? It is a single command and no prerequisites:
+
+```bash
+curl -fsSL https://astral.sh/uv/install.sh | sh          # macOS, Linux
+powershell -c "irm https://astral.sh/uv/install.ps1|iex" # Windows
+```
+
+### Upgrade
+
+```bash
+uv tool upgrade elva-cli      # or: pipx upgrade elva-cli
+```
+
+### Why not `pip install`?
+
+On Ubuntu, Debian, Fedora and Homebrew macOS, `pip install elva-cli` fails with
+`externally-managed-environment`. Those systems reserve their Python for the OS package
+manager ([PEP 668](https://peps.python.org/pep-0668/)), and `--user` is blocked too.
+
+`uv tool` and `pipx` are the supported way to install a Python command-line application:
+they give it a private environment and put just the `elva` command on your `PATH`, so it
+can never conflict with your projects' dependencies.
+
+Inside an already-activated virtualenv, `pip install elva-cli` works fine.
+
+## Requirements
+
+- Python 3.11 or newer (bundled automatically if you install via `uv tool`)
+- An [Elva](https://getelva.ai) account
+
+## Links
+
+- [Elva](https://getelva.ai)
+- [Issues](https://github.com/Theneo-Inc/theneo-elva-cli/issues)
+- [Contributing](CONTRIBUTING.md)

elva_cli-0.0.3/README.md

@@ -0,0 +1,70 @@
+# Elva CLI
+
+Manage your [Elva](https://getelva.ai) API projects from the terminal: import specs,
+inspect collections, and generate MCP servers without opening a browser.
+
+> **Early alpha.** The command surface is still taking shape. This release ships
+> `--version` and `--help` only; the first working commands land in `0.1.0`.
+
+## Install
+
+Requires Python 3.11 or newer.
+
+```bash
+uv tool install elva-cli
+```
+
+Or with [pipx](https://pipx.pypa.io/), if you already use it:
+
+```bash
+pipx install elva-cli
+```
+
+Either way, `elva` is then available from any directory:
+
+```bash
+elva --version
+elva --help
+```
+
+To try it without installing anything:
+
+```bash
+uvx --from elva-cli elva --version
+```
+
+Don't have `uv`? It is a single command and no prerequisites:
+
+```bash
+curl -fsSL https://astral.sh/uv/install.sh | sh          # macOS, Linux
+powershell -c "irm https://astral.sh/uv/install.ps1|iex" # Windows
+```
+
+### Upgrade
+
+```bash
+uv tool upgrade elva-cli      # or: pipx upgrade elva-cli
+```
+
+### Why not `pip install`?
+
+On Ubuntu, Debian, Fedora and Homebrew macOS, `pip install elva-cli` fails with
+`externally-managed-environment`. Those systems reserve their Python for the OS package
+manager ([PEP 668](https://peps.python.org/pep-0668/)), and `--user` is blocked too.
+
+`uv tool` and `pipx` are the supported way to install a Python command-line application:
+they give it a private environment and put just the `elva` command on your `PATH`, so it
+can never conflict with your projects' dependencies.
+
+Inside an already-activated virtualenv, `pip install elva-cli` works fine.
+
+## Requirements
+
+- Python 3.11 or newer (bundled automatically if you install via `uv tool`)
+- An [Elva](https://getelva.ai) account
+
+## Links
+
+- [Elva](https://getelva.ai)
+- [Issues](https://github.com/Theneo-Inc/theneo-elva-cli/issues)
+- [Contributing](CONTRIBUTING.md)

{elva_cli-0.0.2 → elva_cli-0.0.3}/src/elva_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.0.2'
-__version_tuple__ = version_tuple = (0, 0, 2)
+__version__ = version = '0.0.3'
+__version_tuple__ = version_tuple = (0, 0, 3)
 
 __commit_id__ = commit_id = None

elva_cli-0.0.2/PKG-INFO

@@ -1,131 +0,0 @@
-Metadata-Version: 2.5
-Name: elva-cli
-Version: 0.0.2
-Summary: Elva - CLI for Theneo Elva
-Project-URL: Homepage, https://getelva.ai
-Project-URL: Source, https://github.com/Theneo-Inc/theneo-elva-cli
-Project-URL: Issues, https://github.com/Theneo-Inc/theneo-elva-cli/issues
-Author-email: Theneo <support@theneo.io>
-Keywords: api,cli,documentation,elva,openapi,theneo
-Classifier: Development Status :: 3 - Alpha
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Software Development :: Documentation
-Classifier: Typing :: Typed
-Requires-Python: >=3.11
-Requires-Dist: typer<1.0,>=0.15
-Provides-Extra: dev
-Requires-Dist: mypy>=1.11; extra == 'dev'
-Requires-Dist: pytest>=8.2; extra == 'dev'
-Requires-Dist: ruff>=0.6; extra == 'dev'
-Description-Content-Type: text/markdown
-
-# Elva CLI
-
-CLI for Theneo Editor
-
-## Install
-
-Requires Python 3.11 or newer. Pick one:
-
-```bash
-uv tool install elva-cli      # recommended
-pipx install elva-cli         # equivalent, if you already use pipx
-```
-
-`elva` is then available from any directory, no virtualenv to activate:
-
-```bash
-elva --version
-elva --help
-```
-
-To try it without installing anything:
-
-```bash
-uvx --from elva-cli elva --version
-```
-
-### Why not `pip install`?
-
-`pip install elva-cli` into a system Python is blocked on Ubuntu, Debian, Fedora and
-Homebrew macOS by [PEP 668](https://peps.python.org/pep-0668/), which reports
-`externally-managed-environment`. `uv tool` and `pipx` sidestep it by installing into
-an isolated environment for you and putting `elva` on your `PATH` -- which is what you
-want for a command-line tool anyway. Inside an already-activated virtualenv, plain
-`pip install elva-cli` works fine.
-
-### Upgrade
-
-```bash
-uv tool upgrade elva-cli      # or: pipx upgrade elva-cli
-```
-
-
-## Development
-
-Requires Python 3.11 or newer.
-
-```bash
-git clone https://github.com/Theneo-Inc/theneo-elva-cli.git
-cd theneo-elva-cli
-
-python3 -m venv .venv
-source .venv/bin/activate          # Windows: .venv\Scripts\activate
-pip install -e ".[dev]"
-```
-
-`-e` installs in editable mode, so your source edits take effect immediately with
-no reinstall.
-
-Run it:
-
-```bash
-elva --version
-elva --help
-```
-
-```
-$ elva --version
-elva 0.0.1 (python 3.12.3, linux-x86_64)
-```
-
-`python -m elva_cli --version` runs the same entry point, if you prefer that form.
-
-
-### With uv (faster)
-
-If you have [uv](https://docs.astral.sh/uv/), it replaces the venv and pip steps:
-
-```bash
-uv sync --extra dev
-uv run elva --version
-```
-
-#### Running `elva` from any directory (development)
-
-To activate everywhere locally:
-
-```bash
-uv tool install --editable ~/Desktop/theneo-elva-cli
-```
-
-### Checks
-
-```bash
-ruff check .        # lint
-ruff format .       # format
-mypy                # types, strict
-```
-
-### Version numbers
-
-The version comes from the git tag via `hatch-vcs` -- there is nothing to bump by hand.
-An untagged checkout reports something like `0.0.post1.dev2+gc657326`, which PyPI will
-not accept; a tagged one reports a clean `0.0.1`.
-
-To cut a release, see [RELEASING.md](RELEASING.md).
-

elva_cli-0.0.2/README.md

@@ -1,106 +0,0 @@
-# Elva CLI
-
-CLI for Theneo Editor
-
-## Install
-
-Requires Python 3.11 or newer. Pick one:
-
-```bash
-uv tool install elva-cli      # recommended
-pipx install elva-cli         # equivalent, if you already use pipx
-```
-
-`elva` is then available from any directory, no virtualenv to activate:
-
-```bash
-elva --version
-elva --help
-```
-
-To try it without installing anything:
-
-```bash
-uvx --from elva-cli elva --version
-```
-
-### Why not `pip install`?
-
-`pip install elva-cli` into a system Python is blocked on Ubuntu, Debian, Fedora and
-Homebrew macOS by [PEP 668](https://peps.python.org/pep-0668/), which reports
-`externally-managed-environment`. `uv tool` and `pipx` sidestep it by installing into
-an isolated environment for you and putting `elva` on your `PATH` -- which is what you
-want for a command-line tool anyway. Inside an already-activated virtualenv, plain
-`pip install elva-cli` works fine.
-
-### Upgrade
-
-```bash
-uv tool upgrade elva-cli      # or: pipx upgrade elva-cli
-```
-
-
-## Development
-
-Requires Python 3.11 or newer.
-
-```bash
-git clone https://github.com/Theneo-Inc/theneo-elva-cli.git
-cd theneo-elva-cli
-
-python3 -m venv .venv
-source .venv/bin/activate          # Windows: .venv\Scripts\activate
-pip install -e ".[dev]"
-```
-
-`-e` installs in editable mode, so your source edits take effect immediately with
-no reinstall.
-
-Run it:
-
-```bash
-elva --version
-elva --help
-```
-
-```
-$ elva --version
-elva 0.0.1 (python 3.12.3, linux-x86_64)
-```
-
-`python -m elva_cli --version` runs the same entry point, if you prefer that form.
-
-
-### With uv (faster)
-
-If you have [uv](https://docs.astral.sh/uv/), it replaces the venv and pip steps:
-
-```bash
-uv sync --extra dev
-uv run elva --version
-```
-
-#### Running `elva` from any directory (development)
-
-To activate everywhere locally:
-
-```bash
-uv tool install --editable ~/Desktop/theneo-elva-cli
-```
-
-### Checks
-
-```bash
-ruff check .        # lint
-ruff format .       # format
-mypy                # types, strict
-```
-
-### Version numbers
-
-The version comes from the git tag via `hatch-vcs` -- there is nothing to bump by hand.
-An untagged checkout reports something like `0.0.post1.dev2+gc657326`, which PyPI will
-not accept; a tagged one reports a clean `0.0.1`.
-
-To cut a release, see [RELEASING.md](RELEASING.md).
-