| Name | weco JSON |
| Version |
0.2.25
JSON |
| download |
| home_page | None |
| Summary | Documentation for `weco`, a CLI for using Weco AI's code optimizer. |
| upload_time | 2025-07-30 16:33:24 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | MIT |
| keywords |
ai
code optimization
code generation
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<div align="center">
<div align="center">
<img src="assets/weco.svg" alt="Weco Logo" width="120" height="120" style="margin-bottom: 20px;">
<h1>Weco: The Platform for Self-Improving Code</h1>
</div>
[](https://www.python.org)
[](https://badge.fury.io/py/weco)
[](https://docs.weco.ai/)
[](https://pepy.tech/projects/weco)
[](https://arxiv.org/abs/2502.13138)
[](https://colab.research.google.com/github/WecoAI/weco-cli/blob/main/examples/hello-kernel-world/colab_notebook_walkthrough.ipynb)
`pip install weco`
</div>
---
Weco systematically optimizes your code, guided directly by your evaluation metrics.
Example applications include:
- **GPU Kernel Optimization**: Reimplement PyTorch functions using [CUDA](/examples/cuda/README.md) or [Triton](/examples/triton/README.md), optimizing for `latency`, `throughput`, or `memory_bandwidth`.
- **Model Development**: Tune feature transformations, architectures or [the whole training pipeline](/examples/spaceship-titanic/README.md), optimizing for `validation_accuracy`, `AUC`, or `Sharpe Ratio`.
- **Prompt Engineering**: Refine prompts for LLMs (e.g., for [math problems](/examples/prompt/README.md)), optimizing for `win_rate`, `relevance`, or `format_adherence`
---
## Overview
The `weco` CLI leverages a tree search approach guided by LLMs to iteratively explore and refine your code. It automatically applies changes, runs your evaluation script, parses the results, and proposes further improvements based on the specified goal.
---
## Setup
1. **Install the Package:**
```bash
pip install weco
```
2. **Set Up LLM API Keys (Required):**
`weco` requires API keys for the LLMs it uses internally. You **must** provide these keys via environment variables:
- **OpenAI:** `export OPENAI_API_KEY="your_key_here"` (Create your OpenAI API key [here](https://platform.openai.com/api-keys))
- **Anthropic:** `export ANTHROPIC_API_KEY="your_key_here"` (Create your Anthropic API key [here](https://console.anthropic.com/settings/keys))
- **Google:** `export GEMINI_API_KEY="your_key_here"` (Google AI Studio has a free API usage quota. Create your Gemini API key [here](https://aistudio.google.com/apikey) to use `weco` for free.)
---
## Get Started
### Quick Start (Recommended for New Users)
The easiest way to get started with Weco is to use the **interactive copilot**. Simply navigate to your project directory and run:
```bash
weco
```
Or specify a project path:
```bash
weco /path/to/your/project
```
This launches Weco's interactive copilot that will:
1. **Analyze your codebase** using AI to understand your project structure and identify optimization opportunities
2. **Suggest specific optimizations** tailored to your code (e.g., GPU kernel optimization, model improvements, prompt engineering)
3. **Generate evaluation scripts** automatically or help you configure existing ones
4. **Set up the complete optimization pipeline** with appropriate metrics and commands
5. **Run the optimization** or provide you with the exact command to execute
<div style="background-color: #fff3cd; border: 1px solid #ffeeba; padding: 15px; border-radius: 4px; margin-bottom: 15px;">
<strong>⚠️ Warning: Code Modification</strong><br>
<code>weco</code> directly modifies the file specified by <code>--source</code> during the optimization process. It is <strong>strongly recommended</strong> to use version control (like Git) to track changes and revert if needed. Alternatively, ensure you have a backup of your original file before running the command. Upon completion, the file will contain the best-performing version of the code found during the run.
</div>
### Manual Setup
**Configure optimization parameters yourself** - If you need precise control over the optimization parameters, you can use the direct `weco run` command:
**Example: Optimizing Simple PyTorch Operations**
```bash
# Navigate to the example directory
cd examples/hello-kernel-world
# Install dependencies
pip install torch
# Run Weco with manual configuration
weco run --source optimize.py \
--eval-command "python evaluate.py --solution-path optimize.py --device cpu" \
--metric speedup \
--goal maximize \
--steps 15 \
--additional-instructions "Fuse operations in the forward method while ensuring the max float deviation remains small. Maintain the same format of the code."
```
**Note:** If you have an NVIDIA GPU, change the device in the `--eval-command` to `cuda`. If you are running this on Apple Silicon, set it to `mps`.
For more advanced examples, including [Triton](/examples/triton/README.md), [CUDA kernel optimization](/examples/cuda/README.md), [ML model optimization](/examples/spaceship-titanic/README.md), and [prompt engineering for math problems](examples/prompt/README.md), please see the `README.md` files within the corresponding subdirectories under the [`examples/`](examples/) folder.
---
### Arguments for `weco run`
**Required:**
| Argument | Description | Example |
| :------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------- |
| `-s, --source` | Path to the source code file that will be optimized. | `-s model.py` |
| `-c, --eval-command`| Command to run for evaluating the code in `--source`. This command should print the target `--metric` and its value to the terminal (stdout/stderr). See note below. | `-c "python eval.py"` |
| `-m, --metric` | The name of the metric you want to optimize (e.g., 'accuracy', 'speedup', 'loss'). This metric name does not need to match what's printed by your `--eval-command` exactly (e.g., its okay to use "speedup" instead of "Speedup:"). | `-m speedup` |
| `-g, --goal` | `maximize`/`max` to maximize the `--metric` or `minimize`/`min` to minimize it. | `-g maximize` |
<br>
**Optional:**
| Argument | Description | Default | Example |
| :----------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------ | :------------------ |
| `-n, --steps` | Number of optimization steps (LLM iterations) to run. | 100 | `-n 50` |
| `-M, --model` | Model identifier for the LLM to use (e.g., `o4-mini`, `claude-sonnet-4-0`). | `o4-mini` when `OPENAI_API_KEY` is set; `claude-sonnet-4-0` when `ANTHROPIC_API_KEY` is set; `gemini-2.5-pro` when `GEMINI_API_KEY` is set. | `-M o4-mini` |
| `-i, --additional-instructions`| Natural language description of specific instructions **or** path to a file containing detailed instructions to guide the LLM. | `None` | `-i instructions.md` or `-i "Optimize the model for faster inference"`|
| `-l, --log-dir` | Path to the directory to log intermediate steps and final optimization result. | `.runs/` | `-l ./logs/` |
| `--eval-timeout` | Timeout in seconds for each step in evaluation. | No timeout (unlimited) | `--eval-timeout 3600` |
---
### Authentication & Dashboard
Weco offers both **anonymous** and **authenticated** usage:
#### Anonymous Usage
You can use Weco without creating an account by providing LLM API keys via environment variables. This is perfect for trying out Weco or for users who prefer not to create accounts.
#### Authenticated Usage (Recommended)
To save your optimization runs and view them on the Weco dashboard, you can log in using Weco's secure device authentication flow:
1. **During onboarding**: When you run `weco` for the first time, you'll be prompted to log in or skip
2. **Manual login**: Use `weco logout` to clear credentials, then run `weco` again to re-authenticate
3. **Device flow**: Weco will open your browser automatically and guide you through a secure OAuth-style authentication
**Benefits of authenticated usage:**
- **Run history**: View all your optimization runs on the Weco dashboard
- **Progress tracking**: Monitor long-running optimizations remotely
- **Enhanced support**: Get better assistance with your optimization challenges
---
## Command Reference
### Basic Usage Patterns
| Command | Description | When to Use |
|---------|-------------|-------------|
| `weco` | Launch interactive onboarding | **Recommended for beginners** - Analyzes your codebase and guides you through setup |
| `weco /path/to/project` | Launch onboarding for specific project | When working with a project in a different directory |
| `weco run [options]` | Direct optimization execution | **For advanced users** - When you know exactly what to optimize and how |
| `weco logout` | Clear authentication credentials | To switch accounts or troubleshoot authentication issues |
### Model Selection
You can specify which LLM model to use with the `-M` or `--model` flag:
```bash
# Use with onboarding
weco --model gpt-4o
# Use with direct execution
weco run --model claude-3.5-sonnet --source optimize.py [other options...]
```
**Available models:**
- `gpt-4o`, `o4-mini` (requires `OPENAI_API_KEY`)
- `claude-3.5-sonnet`, `claude-sonnet-4-20250514` (requires `ANTHROPIC_API_KEY`)
- `gemini-2.5-pro` (requires `GEMINI_API_KEY`)
If no model is specified, Weco automatically selects the best available model based on your API keys.
---
### Performance & Expectations
Weco, powered by the AIDE algorithm, optimizes code iteratively based on your evaluation results. Achieving significant improvements, especially on complex research-level tasks, often requires substantial exploration time.
The following plot from the independent [Research Engineering Benchmark (RE-Bench)](https://metr.org/AI_R_D_Evaluation_Report.pdf) report shows the performance of AIDE (the algorithm behind Weco) on challenging ML research engineering tasks over different time budgets.
<p align="center">
<img src="https://github.com/user-attachments/assets/ff0e471d-2f50-4e2d-b718-874862f533df" alt="RE-Bench Performance Across Time" width="60%"/>
</p>
As shown, AIDE demonstrates strong performance gains over time, surpassing lower human expert percentiles within hours and continuing to improve. This highlights the potential of evaluation-driven optimization but also indicates that reaching high levels of performance comparable to human experts on difficult benchmarks can take considerable time (tens of hours in this specific benchmark, corresponding to many `--steps` in the Weco CLI). Factor this into your planning when setting the number of `--steps` for your optimization runs.
---
### Important Note on Evaluation
The command specified by `--eval-command` is crucial. It's responsible for executing the potentially modified code from `--source` and assessing its performance. **This command MUST print the metric you specified with `--metric` along with its numerical value to the terminal (standard output or standard error).** Weco reads this output to understand how well each code version performs and guide the optimization process.
For example, if you set `--metric speedup`, your evaluation script (`eval.py` in the examples) should output a line like:
```
speedup: 1.5
```
or
```
Final speedup value = 1.5
```
Weco will parse this output to extract the numerical value (1.5 in this case) associated with the metric name ('speedup').
## Supported Models
Weco supports the following LLM models:
### OpenAI Models
- `o3`
- `o3-mini`
- `o4-mini`
- `o1-pro`
- `o1`
- `gpt-4.1`
- `gpt-4.1-mini`
- `gpt-4.1-nano`
- `gpt-4o`
- `gpt-4o-mini`
### Anthropic Models
- `claude-opus-4-0`
- `claude-sonnet-4-0`
- `claude-3-7-sonnet-latest`
### Gemini Models
- `gemini-2.5-pro`
- `gemini-2.5-flash`
- `gemini-2.5-flash-lite`
You can specify any of these models using the `-M` or `--model` flag. Ensure you have the corresponding API key set as an environment variable for the model provider you wish to use.
---
## Contributing
We welcome contributions! Please see [contributing.md](contributing.md) for detailed guidelines on how to contribute to this project.
---
Raw data
{
"_id": null,
"home_page": null,
"name": "weco",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "AI, Code Optimization, Code Generation",
"author": null,
"author_email": "Weco AI Team <contact@weco.ai>",
"download_url": "https://files.pythonhosted.org/packages/4f/f5/e5adbdf98d298b08c52fabd6bdea454c516d3722e8fa0e20c3c53e88b803/weco-0.2.25.tar.gz",
"platform": null,
"description": "<div align=\"center\">\n\n<div align=\"center\">\n <img src=\"assets/weco.svg\" alt=\"Weco Logo\" width=\"120\" height=\"120\" style=\"margin-bottom: 20px;\">\n <h1>Weco: The Platform for Self-Improving Code</h1>\n</div>\n\n[](https://www.python.org)\n[](https://badge.fury.io/py/weco)\n[](https://docs.weco.ai/)\n[](https://pepy.tech/projects/weco)\n[](https://arxiv.org/abs/2502.13138)\n[](https://colab.research.google.com/github/WecoAI/weco-cli/blob/main/examples/hello-kernel-world/colab_notebook_walkthrough.ipynb)\n\n`pip install weco`\n\n</div>\n\n---\n\nWeco systematically optimizes your code, guided directly by your evaluation metrics.\n\nExample applications include:\n\n- **GPU Kernel Optimization**: Reimplement PyTorch functions using [CUDA](/examples/cuda/README.md) or [Triton](/examples/triton/README.md), optimizing for `latency`, `throughput`, or `memory_bandwidth`.\n- **Model Development**: Tune feature transformations, architectures or [the whole training pipeline](/examples/spaceship-titanic/README.md), optimizing for `validation_accuracy`, `AUC`, or `Sharpe Ratio`.\n- **Prompt Engineering**: Refine prompts for LLMs (e.g., for [math problems](/examples/prompt/README.md)), optimizing for `win_rate`, `relevance`, or `format_adherence`\n\n\n\n---\n\n## Overview\n\nThe `weco` CLI leverages a tree search approach guided by LLMs to iteratively explore and refine your code. It automatically applies changes, runs your evaluation script, parses the results, and proposes further improvements based on the specified goal.\n\n\n\n---\n\n## Setup\n\n1. **Install the Package:**\n\n ```bash\n pip install weco\n ```\n\n2. **Set Up LLM API Keys (Required):**\n\n `weco` requires API keys for the LLMs it uses internally. You **must** provide these keys via environment variables:\n\n - **OpenAI:** `export OPENAI_API_KEY=\"your_key_here\"` (Create your OpenAI API key [here](https://platform.openai.com/api-keys))\n - **Anthropic:** `export ANTHROPIC_API_KEY=\"your_key_here\"` (Create your Anthropic API key [here](https://console.anthropic.com/settings/keys))\n - **Google:** `export GEMINI_API_KEY=\"your_key_here\"` (Google AI Studio has a free API usage quota. Create your Gemini API key [here](https://aistudio.google.com/apikey) to use `weco` for free.)\n\n---\n\n## Get Started\n\n### Quick Start (Recommended for New Users)\n\nThe easiest way to get started with Weco is to use the **interactive copilot**. Simply navigate to your project directory and run:\n\n```bash\nweco\n```\n\nOr specify a project path:\n\n```bash\nweco /path/to/your/project\n```\n\nThis launches Weco's interactive copilot that will:\n\n1. **Analyze your codebase** using AI to understand your project structure and identify optimization opportunities\n2. **Suggest specific optimizations** tailored to your code (e.g., GPU kernel optimization, model improvements, prompt engineering)\n3. **Generate evaluation scripts** automatically or help you configure existing ones\n4. **Set up the complete optimization pipeline** with appropriate metrics and commands\n5. **Run the optimization** or provide you with the exact command to execute\n\n<div style=\"background-color: #fff3cd; border: 1px solid #ffeeba; padding: 15px; border-radius: 4px; margin-bottom: 15px;\">\n <strong>\u26a0\ufe0f Warning: Code Modification</strong><br>\n <code>weco</code> directly modifies the file specified by <code>--source</code> during the optimization process. It is <strong>strongly recommended</strong> to use version control (like Git) to track changes and revert if needed. Alternatively, ensure you have a backup of your original file before running the command. Upon completion, the file will contain the best-performing version of the code found during the run.\n</div>\n\n### Manual Setup\n\n**Configure optimization parameters yourself** - If you need precise control over the optimization parameters, you can use the direct `weco run` command:\n\n**Example: Optimizing Simple PyTorch Operations**\n\n```bash\n# Navigate to the example directory\ncd examples/hello-kernel-world\n\n# Install dependencies\npip install torch\n\n# Run Weco with manual configuration\nweco run --source optimize.py \\\n --eval-command \"python evaluate.py --solution-path optimize.py --device cpu\" \\\n --metric speedup \\\n --goal maximize \\\n --steps 15 \\\n --additional-instructions \"Fuse operations in the forward method while ensuring the max float deviation remains small. Maintain the same format of the code.\"\n```\n\n**Note:** If you have an NVIDIA GPU, change the device in the `--eval-command` to `cuda`. If you are running this on Apple Silicon, set it to `mps`.\n\nFor more advanced examples, including [Triton](/examples/triton/README.md), [CUDA kernel optimization](/examples/cuda/README.md), [ML model optimization](/examples/spaceship-titanic/README.md), and [prompt engineering for math problems](examples/prompt/README.md), please see the `README.md` files within the corresponding subdirectories under the [`examples/`](examples/) folder.\n\n---\n\n### Arguments for `weco run`\n\n**Required:**\n\n| Argument | Description | Example |\n| :------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------- |\n| `-s, --source` | Path to the source code file that will be optimized. | `-s model.py` |\n| `-c, --eval-command`| Command to run for evaluating the code in `--source`. This command should print the target `--metric` and its value to the terminal (stdout/stderr). See note below. | `-c \"python eval.py\"` |\n| `-m, --metric` | The name of the metric you want to optimize (e.g., 'accuracy', 'speedup', 'loss'). This metric name does not need to match what's printed by your `--eval-command` exactly (e.g., its okay to use \"speedup\" instead of \"Speedup:\"). | `-m speedup` |\n| `-g, --goal` | `maximize`/`max` to maximize the `--metric` or `minimize`/`min` to minimize it. | `-g maximize` |\n\n<br>\n\n**Optional:**\n\n| Argument | Description | Default | Example |\n| :----------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------ | :------------------ |\n| `-n, --steps` | Number of optimization steps (LLM iterations) to run. | 100 | `-n 50` |\n| `-M, --model` | Model identifier for the LLM to use (e.g., `o4-mini`, `claude-sonnet-4-0`). | `o4-mini` when `OPENAI_API_KEY` is set; `claude-sonnet-4-0` when `ANTHROPIC_API_KEY` is set; `gemini-2.5-pro` when `GEMINI_API_KEY` is set. | `-M o4-mini` |\n| `-i, --additional-instructions`| Natural language description of specific instructions **or** path to a file containing detailed instructions to guide the LLM. | `None` | `-i instructions.md` or `-i \"Optimize the model for faster inference\"`|\n| `-l, --log-dir` | Path to the directory to log intermediate steps and final optimization result. | `.runs/` | `-l ./logs/` |\n| `--eval-timeout` | Timeout in seconds for each step in evaluation. | No timeout (unlimited) | `--eval-timeout 3600` |\n\n---\n\n### Authentication & Dashboard\n\nWeco offers both **anonymous** and **authenticated** usage:\n\n#### Anonymous Usage\nYou can use Weco without creating an account by providing LLM API keys via environment variables. This is perfect for trying out Weco or for users who prefer not to create accounts.\n\n#### Authenticated Usage (Recommended)\nTo save your optimization runs and view them on the Weco dashboard, you can log in using Weco's secure device authentication flow:\n\n1. **During onboarding**: When you run `weco` for the first time, you'll be prompted to log in or skip\n2. **Manual login**: Use `weco logout` to clear credentials, then run `weco` again to re-authenticate\n3. **Device flow**: Weco will open your browser automatically and guide you through a secure OAuth-style authentication\n\n\n\n**Benefits of authenticated usage:**\n- **Run history**: View all your optimization runs on the Weco dashboard\n- **Progress tracking**: Monitor long-running optimizations remotely\n- **Enhanced support**: Get better assistance with your optimization challenges\n\n---\n\n## Command Reference\n\n### Basic Usage Patterns\n\n| Command | Description | When to Use |\n|---------|-------------|-------------|\n| `weco` | Launch interactive onboarding | **Recommended for beginners** - Analyzes your codebase and guides you through setup |\n| `weco /path/to/project` | Launch onboarding for specific project | When working with a project in a different directory |\n| `weco run [options]` | Direct optimization execution | **For advanced users** - When you know exactly what to optimize and how |\n| `weco logout` | Clear authentication credentials | To switch accounts or troubleshoot authentication issues |\n\n### Model Selection\n\nYou can specify which LLM model to use with the `-M` or `--model` flag:\n\n```bash\n# Use with onboarding\nweco --model gpt-4o\n\n# Use with direct execution\nweco run --model claude-3.5-sonnet --source optimize.py [other options...]\n```\n\n**Available models:**\n- `gpt-4o`, `o4-mini` (requires `OPENAI_API_KEY`)\n- `claude-3.5-sonnet`, `claude-sonnet-4-20250514` (requires `ANTHROPIC_API_KEY`)\n- `gemini-2.5-pro` (requires `GEMINI_API_KEY`)\n\nIf no model is specified, Weco automatically selects the best available model based on your API keys.\n\n---\n\n### Performance & Expectations\n\nWeco, powered by the AIDE algorithm, optimizes code iteratively based on your evaluation results. Achieving significant improvements, especially on complex research-level tasks, often requires substantial exploration time.\n\nThe following plot from the independent [Research Engineering Benchmark (RE-Bench)](https://metr.org/AI_R_D_Evaluation_Report.pdf) report shows the performance of AIDE (the algorithm behind Weco) on challenging ML research engineering tasks over different time budgets.\n\n<p align=\"center\">\n<img src=\"https://github.com/user-attachments/assets/ff0e471d-2f50-4e2d-b718-874862f533df\" alt=\"RE-Bench Performance Across Time\" width=\"60%\"/>\n</p>\n\nAs shown, AIDE demonstrates strong performance gains over time, surpassing lower human expert percentiles within hours and continuing to improve. This highlights the potential of evaluation-driven optimization but also indicates that reaching high levels of performance comparable to human experts on difficult benchmarks can take considerable time (tens of hours in this specific benchmark, corresponding to many `--steps` in the Weco CLI). Factor this into your planning when setting the number of `--steps` for your optimization runs.\n\n---\n\n### Important Note on Evaluation\n\nThe command specified by `--eval-command` is crucial. It's responsible for executing the potentially modified code from `--source` and assessing its performance. **This command MUST print the metric you specified with `--metric` along with its numerical value to the terminal (standard output or standard error).** Weco reads this output to understand how well each code version performs and guide the optimization process.\n\nFor example, if you set `--metric speedup`, your evaluation script (`eval.py` in the examples) should output a line like:\n\n```\nspeedup: 1.5\n```\n\nor\n\n```\nFinal speedup value = 1.5\n```\n\nWeco will parse this output to extract the numerical value (1.5 in this case) associated with the metric name ('speedup').\n\n## Supported Models\n\nWeco supports the following LLM models:\n\n### OpenAI Models\n- `o3`\n- `o3-mini`\n- `o4-mini`\n- `o1-pro`\n- `o1`\n- `gpt-4.1`\n- `gpt-4.1-mini`\n- `gpt-4.1-nano`\n- `gpt-4o`\n- `gpt-4o-mini`\n\n### Anthropic Models\n- `claude-opus-4-0`\n- `claude-sonnet-4-0`\n- `claude-3-7-sonnet-latest`\n\n### Gemini Models\n- `gemini-2.5-pro`\n- `gemini-2.5-flash`\n- `gemini-2.5-flash-lite`\n\nYou can specify any of these models using the `-M` or `--model` flag. Ensure you have the corresponding API key set as an environment variable for the model provider you wish to use.\n\n---\n\n## Contributing\n\nWe welcome contributions! Please see [contributing.md](contributing.md) for detailed guidelines on how to contribute to this project.\n\n---\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Documentation for `weco`, a CLI for using Weco AI's code optimizer.",
"version": "0.2.25",
"project_urls": {
"Homepage": "https://github.com/WecoAI/weco-cli"
},
"split_keywords": [
"ai",
" code optimization",
" code generation"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "574fd4f75f963131fd498557afbcb2db547d0a499a032a5a24f626f4fa5fae72",
"md5": "81040f00c8a9aac04ae7437c80f3a2bf",
"sha256": "5fdfd92851acf37cacaefa14a943f6aef345ace998f72565227b53bfefd74e7f"
},
"downloads": -1,
"filename": "weco-0.2.25-py3-none-any.whl",
"has_sig": false,
"md5_digest": "81040f00c8a9aac04ae7437c80f3a2bf",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 38440,
"upload_time": "2025-07-30T16:33:22",
"upload_time_iso_8601": "2025-07-30T16:33:22.388554Z",
"url": "https://files.pythonhosted.org/packages/57/4f/d4f75f963131fd498557afbcb2db547d0a499a032a5a24f626f4fa5fae72/weco-0.2.25-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "4ff5e5adbdf98d298b08c52fabd6bdea454c516d3722e8fa0e20c3c53e88b803",
"md5": "8c23fff98590133526a650f130620784",
"sha256": "920179c4f9a5177f8489db1cd87628ff98813e6dd75772eb2524d7ed490e5fce"
},
"downloads": -1,
"filename": "weco-0.2.25.tar.gz",
"has_sig": false,
"md5_digest": "8c23fff98590133526a650f130620784",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 39464271,
"upload_time": "2025-07-30T16:33:24",
"upload_time_iso_8601": "2025-07-30T16:33:24.338857Z",
"url": "https://files.pythonhosted.org/packages/4f/f5/e5adbdf98d298b08c52fabd6bdea454c516d3722e8fa0e20c3c53e88b803/weco-0.2.25.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-07-30 16:33:24",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "WecoAI",
"github_project": "weco-cli",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "weco"
}
