chefe 0.0.1__tar.gz

chefe-0.0.1/.coderabbit.yaml

@@ -0,0 +1,12 @@
+# https://docs.coderabbit.ai/guides/configure-coderabbit
+language: en
+reviews:
+  profile: chill
+  request_changes_workflow: false
+  high_level_summary: true
+  poem: false
+  auto_review:
+    enabled: true
+    drafts: false
+chat:
+  auto_reply: true

chefe-0.0.1/.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly

chefe-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python }}
+          enable-cache: true
+      - run: uv sync --extra dev
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run mypy src
+      - run: uv run pyrefly check
+      - run: uv run pytest -q

chefe-0.0.1/.github/workflows/docs.yml

@@ -0,0 +1,37 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+    paths: ["docs/**", "mkdocs.yml", ".github/workflows/docs.yml"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv run --extra docs mkdocs build -d site
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

chefe-0.0.1/.github/workflows/publish.yml

@@ -0,0 +1,19 @@
+name: Publish
+
+# Publishes to PyPI on a version tag via Trusted Publishing (OIDC, no token to store).
+# Configure the trusted publisher once at https://pypi.org/manage/account/publishing/
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1

chefe-0.0.1/.gitignore

@@ -0,0 +1,19 @@
+# chefe's own generated env + manifests
+.chefe/
+
+# python
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+
+# tooling
+.ruff_cache/
+.pytest_cache/
+.hypothesis/
+.coverage
+htmlcov/
+.mypy_cache/
+.pyrefly/

chefe-0.0.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

chefe-0.0.1/PKG-INFO

@@ -0,0 +1,112 @@
+Metadata-Version: 2.4
+Name: chefe
+Version: 0.0.1
+Summary: One manifest for every package manager | conda, PyPI, npm, cargo & more, behind a single file.
+Project-URL: Homepage, https://github.com/phvv-me/chefe
+Project-URL: Repository, https://github.com/phvv-me/chefe
+Project-URL: Issues, https://github.com/phvv-me/chefe/issues
+Author-email: Pedro Valois <contact@phvv.me>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: cargo,conda,monorepo,npm,package-manager,pixi,polyglot,pypi
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: System :: Software Distribution
+Requires-Python: >=3.11
+Requires-Dist: cyclopts>=4
+Requires-Dist: packaging>=24
+Requires-Dist: plumbum>=1.8
+Requires-Dist: pydantic>=2.7
+Requires-Dist: rich>=13
+Requires-Dist: tomlkit>=0.13
+Requires-Dist: typing-extensions>=4.6
+Provides-Extra: dev
+Requires-Dist: dirty-equals>=0.8; extra == 'dev'
+Requires-Dist: faker>=30; extra == 'dev'
+Requires-Dist: hypothesis>=6.100; extra == 'dev'
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pyrefly>=1; extra == 'dev'
+Requires-Dist: pytest-cov>=5; extra == 'dev'
+Requires-Dist: pytest-mock>=3.14; extra == 'dev'
+Requires-Dist: pytest-subprocess>=1.5; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Requires-Dist: syrupy>=4; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocs-llmstxt>=0.2; extra == 'docs'
+Requires-Dist: mkdocs-material>=9.5; extra == 'docs'
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+<img src="docs/assets/logo.svg" width="148" alt="chefe logo, a domed serving cloche" />
+
+# chefe
+
+**One manifest for every package manager.** 🧑‍🍳
+
+[![CI](https://github.com/phvv-me/chefe/actions/workflows/ci.yml/badge.svg)](https://github.com/phvv-me/chefe/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/chefe.svg?color=EAB308)](https://pypi.org/project/chefe/)
+[![Docs](https://img.shields.io/badge/docs-phvv.me%2Fchefe-EAB308)](https://phvv.me/chefe)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+</div>
+
+> [!WARNING]
+> **chefe is early (`0.0.x`).** The manifest and commands may still change.
+
+## Installation
+
+```sh
+curl -fsSL https://phvv.me/chefe/install.sh | sh
+```
+
+This installs [pixi](https://pixi.sh) (the engine chefe compiles to) and chefe itself. Prefer the raw package? Use `pip install chefe` or `uv tool install chefe`.
+
+## What it is
+
+Conda, PyPI, npm, cargo. Real projects need several at once, scattered across `pixi.toml`, `package.json`, and `Cargo.toml`. chefe is the head chef. You write **one `chefe.toml`** recipe, chefe runs the line (pixi, npm, cargo) and plates a single environment. It never re-implements a solver. It runs the cooks.
+
+```toml
+[workspace]
+name     = "my-project"
+channels = ["conda-forge"]
+
+[deps]                      # bare table is conda, the default source
+python  = ">=3.11"
+ripgrep = "*"
+
+[pypi.deps]                 # resolved by pixi-via-uv, in the same env
+torch = ">=2.6"
+
+[cargo.deps]                # other ecosystems are explicit via [<eco>.deps]
+bookokrat = "*"
+
+[npm.deps]
+prettier = ">=3"
+```
+
+## Usage
+
+```sh
+chefe init                 # scaffold a chefe.toml
+chefe add ripgrep          # add deps, use --pypi / --cargo / --npm for others
+chefe install              # provision every ecosystem at once
+chefe tree                 # what's declared vs installed, per ecosystem
+```
+
+> [!TIP]
+> Run `chefe tree` anytime to see declared vs installed across every ecosystem at a glance. ✅
+
+> [!NOTE]
+> Full documentation lives at **[phvv.me/chefe](https://phvv.me/chefe)**.
+
+## Lore
+
+A head chef never cooks every dish alone. They write the recipe and run the line, and the cooks each work their station. chefe does the same for your dependencies. One recipe in, one plated environment out, with pixi, npm, and cargo working the stations. 🧑‍🍳

chefe-0.0.1/README.md

@@ -0,0 +1,67 @@
+<div align="center">
+
+<img src="docs/assets/logo.svg" width="148" alt="chefe logo, a domed serving cloche" />
+
+# chefe
+
+**One manifest for every package manager.** 🧑‍🍳
+
+[![CI](https://github.com/phvv-me/chefe/actions/workflows/ci.yml/badge.svg)](https://github.com/phvv-me/chefe/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/chefe.svg?color=EAB308)](https://pypi.org/project/chefe/)
+[![Docs](https://img.shields.io/badge/docs-phvv.me%2Fchefe-EAB308)](https://phvv.me/chefe)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+</div>
+
+> [!WARNING]
+> **chefe is early (`0.0.x`).** The manifest and commands may still change.
+
+## Installation
+
+```sh
+curl -fsSL https://phvv.me/chefe/install.sh | sh
+```
+
+This installs [pixi](https://pixi.sh) (the engine chefe compiles to) and chefe itself. Prefer the raw package? Use `pip install chefe` or `uv tool install chefe`.
+
+## What it is
+
+Conda, PyPI, npm, cargo. Real projects need several at once, scattered across `pixi.toml`, `package.json`, and `Cargo.toml`. chefe is the head chef. You write **one `chefe.toml`** recipe, chefe runs the line (pixi, npm, cargo) and plates a single environment. It never re-implements a solver. It runs the cooks.
+
+```toml
+[workspace]
+name     = "my-project"
+channels = ["conda-forge"]
+
+[deps]                      # bare table is conda, the default source
+python  = ">=3.11"
+ripgrep = "*"
+
+[pypi.deps]                 # resolved by pixi-via-uv, in the same env
+torch = ">=2.6"
+
+[cargo.deps]                # other ecosystems are explicit via [<eco>.deps]
+bookokrat = "*"
+
+[npm.deps]
+prettier = ">=3"
+```
+
+## Usage
+
+```sh
+chefe init                 # scaffold a chefe.toml
+chefe add ripgrep          # add deps, use --pypi / --cargo / --npm for others
+chefe install              # provision every ecosystem at once
+chefe tree                 # what's declared vs installed, per ecosystem
+```
+
+> [!TIP]
+> Run `chefe tree` anytime to see declared vs installed across every ecosystem at a glance. ✅
+
+> [!NOTE]
+> Full documentation lives at **[phvv.me/chefe](https://phvv.me/chefe)**.
+
+## Lore
+
+A head chef never cooks every dish alone. They write the recipe and run the line, and the cooks each work their station. chefe does the same for your dependencies. One recipe in, one plated environment out, with pixi, npm, and cargo working the stations. 🧑‍🍳

chefe-0.0.1/chefe.toml

@@ -0,0 +1,8 @@
+[workspace]
+name = "proj"
+version = "0.1.0"
+platforms = ["osx-arm64"]
+channels = ["conda-forge"]
+
+[deps]
+python = ">=3.11"

chefe-0.0.1/docs/assets/logo.svg

@@ -0,0 +1,14 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 120" fill="none"
+     stroke="#EAB308" stroke-linecap="round" stroke-linejoin="round">
+  <title>chefe, the cloche at the pass</title>
+  <!-- knob -->
+  <circle cx="50" cy="40" r="3.5" stroke-width="3"/>
+  <path d="M50 43 v6" stroke-width="3"/>
+  <!-- domed lid -->
+  <path d="M20 86 a30 36 0 0 1 60 0" stroke-width="3"/>
+  <!-- inner sheen -->
+  <path d="M33 80 a17 22 0 0 1 12 -20" stroke-width="2.5" opacity="0.55"/>
+  <!-- plate -->
+  <path d="M13 86 h74" stroke-width="3"/>
+  <ellipse cx="50" cy="90" rx="33" ry="5.5" stroke-width="3"/>
+</svg>

chefe-0.0.1/docs/commands.md

@@ -0,0 +1,79 @@
+# Commands
+
+chefe mirrors pixi's verbs over the unified manifest. Most commands take an optional `env` that defaults to `default`.
+
+| command | what it does |
+|---|---|
+| `chefe init` | scaffold a starter `chefe.toml` in the current directory |
+| `chefe sync` | compile `chefe.toml` into `.chefe/{pixi.toml, package.json, …}` |
+| `chefe install [env]` | sync, then provision every ecosystem for `env` |
+| `chefe update [env]` | re-solve to the newest allowed versions across ecosystems |
+| `chefe add <pkg…>` | add packages to the manifest, then re-sync |
+| `chefe remove <pkg…>` | remove packages wherever they're declared, then re-sync |
+| `chefe tree [env]` | declared vs installed, each dep checked in **its own** ecosystem |
+| `chefe run <task> [args…]` | run a task inside the environment |
+| `chefe x <cmd…>` | run a command in a throwaway env, like uvx or pipx run |
+| `chefe shell [env]` | open an activated shell in `env` |
+| `chefe global install [name]` | install the conda deps into the shared global pixi env |
+| `chefe clean` | remove the generated `.chefe/` env and manifests |
+
+## init
+
+```sh
+chefe init                 # name taken from the current directory
+chefe init --name myproj
+```
+
+Writes a minimal `chefe.toml` with the current platform, `conda-forge`, and `python >=3.11`. It refuses to overwrite an existing manifest.
+
+## add
+
+Conda is the default source, and flags pick another ecosystem. `--spec` sets the version (default `*`), while `--env` targets a named environment.
+
+```sh
+chefe add ripgrep numpy
+chefe add torch --pypi --spec ">=2.6"
+chefe add prettier --npm
+chefe add vllm --pypi --env serving
+```
+
+Edits keep your comments and formatting.
+
+## tree
+
+```sh
+chefe tree
+chefe tree serving
+```
+
+Each declared package is checked against the ecosystem it was declared in. Conda goes against the pixi env, npm against `.chefe/node_modules`, and cargo against the env's `.crates.toml`. chefe reports each as `✓` ok, `≠` drift, or `✗` missing, with a transitive count.
+
+## run and shell
+
+```sh
+chefe run build
+chefe shell                # activated shell in the default env
+chefe shell serving
+```
+
+## x
+
+```sh
+chefe x ruff check .                   # run a tool in a throwaway env, no manifest needed
+chefe x --with build python -m build   # add extra packages with --with
+```
+
+Like `uvx` or `pipx run`, `chefe x` provisions an ephemeral environment for the tool and runs it, leaving no `chefe.toml` behind.
+
+## global install
+
+```sh
+chefe global install          # exposes the conda [deps] as a shared global env
+chefe global install mytools
+```
+
+## clean
+
+```sh
+chefe clean                   # wipe .chefe/, a fresh chefe install rebuilds it
+```