semvec/pypi-packages huggingface dataset:
kodi-repo-bootstrap 3.0.3
Bootstrap GIT repo for setting up a Kodi repository
Requires Python: <4.0,>=3.12

# [Kodi](https://kodi.tv/) Repository Bootstrapper
Many thanks to [@Twilight0](https://github.com/Twilight0) and all the others who contributed code for this project before.


## Installation
You can install this Python package via pip(x):

```shell
pip(x) install kodi-repo-bootstrap
```

Otherwise the package can be downloaded from PyPI: https://pypi.org/project/kodi-repo-bootstrap/



## Usage
### 1. Preperations
You need two directories:

- `addons_dir`: This direcotry contains the Kodi addons you want to publish. The single addons can be present as ZIP files or as a directory with the official [Kodi addon structure](https://kodi.wiki/view/Add-on_structure).

    A valid `addons_dir` will look like this:
    ```
    addons_dir/
        |- plugin.addon.id-versionX.zip
        - and / or -
        |- plugin.addon.id/
        |    |- addon.xml
        |    |- ...
        |    - and / or -
        |    |- plugin.addon.id-versionX.zip
    ```
    If multiple versions of the same addon (same ID) are present, only the newest version will be used by the script.

- `repo_dir` where this script creates the necessary structure for a Kodi repository. **Please do not make any manual changes to this directory.**


### 2. Define repository settings
Create a configuration file in JSON format (e.g. `config.json`). An example file with the available options can be found in the root directory of this repository: [config.json.example](https://github.com/mammo0/kodi-repo-bootstrap/blob/master/config.json.example)

**OR**

Configure the Kodi repository with CLI arguments. See
```shell
kodi-repo-bootstrap -h
```
for the available settings.


### 3. Run the script
```shell
kodi-repo-bootstrap <CONFIG_FILE>
```
**The path to the config file is mandatory.**

This will create all files and directories that are necessary for a Kodi repository. No user interaction is needed.


### 4. Publish the `repo_dir` e.g. via HTTP server (webdav)
The `repo_dir` contains all files and directories that are necessary for Kodi to recognize it as a valid repository. You only have to publish it via HTTP.

For a simple Webdav setup with Docker, you can have a look at my other repository: [docker-webdav](https://github.com/mammo0/docker-webdav)


### 5. *[Optional]* Change repository settings
To change any settings you can either

- adjust the config file

**OR**

- use a CLI argument. The script will then save the changes to the config file for you.



## Troubleshooting
If you encounter any errors, please clear the `repo_dir` first and run the script again. This will recreate the Kodi repository file structure.

If the error is still present, feel free to open an issue on GitHub.
semisolve 0.0.1
A flexible Python-based III-V Nitride semiconductor device simulation framework.
Requires Python: >=3.12
Keywords: semiconductor-physics, device-simulation, tcad, nitride-semiconductors, wide-bandgap-semiconductors, heterostructures

# Semisolve: Python-based III-V Nitride Semiconductor Device Simulation Framework

**Semisolve** is a flexible, Python-based simulation framework designed for analyzing the physical behavior of III-V Nitride-based semiconductor heterostructures. 

### Project Status

Semisolve is currently under **active development**. While the core simulation engine is already functional in a private environment, it is undergoing extensive stabilization, feature expansion, and physical validation before its first public release. 

The current version on PyPI (v0.0.1) serves as an initial entry point. The full-featured open-source release is targeted for mid-2026.

Moving beyond traditional "black-box" TCAD tools, Semisolve provides a **"Scriptable TCAD"** environment. It empowers researchers and engineers to define complex device structures, select physical models, and execute high-precision calculations entirely through Python scripts.

---

## Key Features

* **Open & Extensible:** A free, open-source (FOSS) alternative to commercial TCAD, designed for academic transparency and seamless integration into modern data science workflows.
* **Scriptable TCAD:** A "Python-first" approach allowing full control over device definition, material parameters, and simulation loops using NumPy, SciPy, and Pydantic.
* **Data Science Ready:** Seamlessly integrates with the standard Python data stack (NumPy, SciPy, Pandas, Matplotlib). Results are ready for immediate analysis, visualization, and machine learning workflows.
* **Numerical Stability:** Specialized algorithms to overcome extreme concentration gradients and carrier concentration underflow in wide-bandgap semiconductors, ensuring robust convergence via Hybrid Gummel-Newton and precision-aware damping.
* **Nitride Semiconductor-Centric Physics:** Native support for spontaneous and piezoelectric polarization, strain-induced band offsets, and wide-bandgap material properties (GaN/AlGaN/InN).

---

## Current Status

* **Project Founder & Lead Developer:** **Takeru Kumabe** ([@tkrkmb](https://github.com/tkrkmb))
* **Current Phase:** **Private Development.** I am currently specializing in 1D band diagram calculations and self-consistent IV characteristic simulations for III-V Nitride heterostructures.
* **Public Release Target:** **Mid-2026**

## License

This project is licensed under the [Apache License 2.0](LICENSE).

**Disclaimer regarding Intellectual Property:**
This software is developed based on public facts described in academic papers and textbooks. If it infringes upon anyone's intellectual property, please contact the developer, and the relevant parts will be privatized or corrected.

---

## Contact

For inquiries regarding the project's progress or potential collaborations, please reach out via the developer's GitHub profile.
erk 0.7.4
Add your description here
Requires Python: >=3.11

# erk

`erk` is a CLI tool for plan-oriented agentic engineering: create implementation plans with AI, save them to GitHub, execute them in isolated worktrees, and ship code via automated PR workflows.

**[Read the Documentation](https://dagster-io.github.io/erk/)** for complete guides, tutorials, and reference. ([source](docs/))

For the philosophy and design principles behind erk, see [The TAO of erk](TAO.md).

## Quick Start

```bash
# Install prerequisites: python 3.10+, claude, uv, gt, gh

# Install erk in your project
uv add erk && uv sync

# Initialize in your repo
erk init

# Verify setup
erk doctor
```

Then follow [Your First Plan](docs/getting-started/first-plan.md) to learn the workflow.

## The Workflow

The primary workflow: plan → save → implement → ship. **Often completes without touching an IDE.**

```bash
# 1. Plan (in Claude Code)
claude
# → develop plan → save to GitHub issue #42

# 2. Implement
erk implement 42

# 3. Submit PR
erk pr submit

# 4. Address feedback
/erk:pr-address

# 5. Land
erk pr land
```

See [The Workflow](docs/concepts/the-workflow.md) for the complete guide.

## Documentation

| Section                                  | Description                             |
| ---------------------------------------- | --------------------------------------- |
| [Getting Started](docs/getting-started/) | Setup, installation, first tutorial     |
| [Concepts](docs/concepts/)               | Worktrees, stacked PRs, plan mode       |
| [Guides](docs/guides/)                   | Workflows for common tasks              |
| [Reference](docs/reference/)             | Commands, configuration, file locations |
| [Troubleshooting](docs/troubleshooting/) | Common issues and solutions             |
erk-statusline 0.7.4
Custom status line for Claude Code with robbyrussell theme style
Requires Python: >=3.11

# erk-statusline

Custom status line for Claude Code with robbyrussell theme style.

![Screenshot](screenshots/statusline.png)

## Status Line Components

The status line displays (left to right):

- **Git repo**: `(git:repo-name)` - Current GitHub repository name
- **Worktree**: `({wt, br}:name)` or `(wt:name)` - Git worktree info ("root" for main worktree, or worktree name for linked worktrees)
- **Branch**: `(br:branch-name)` - Current git branch (combined with worktree if names match)
- **Current directory**: `(cwd:path)` - Relative path from git root (only shown if not at root)
- **Dirty indicator**: `✗` - Shows when there are uncommitted changes
- **GitHub PR info**: `(gh:#123 plan:#456 st:XX chks:XX)`:
  - `#123` - PR number
  - `plan:#456` - Associated issue number from `.impl/issue.json`
  - `st:` - PR state emoji: `👀` published, `🚧` draft, `🎉` merged, `⛔` closed, `💥` conflicts
  - `chks:` - CI checks status: `✅` passing, `🚫` failing, `🔄` pending
- **Model**: `(S)` Sonnet, `(O)` Opus, or model initial

## Installation

```bash
uv tool install git+https://github.com/dagster-io/erk-statusline
```

Or for development:

```bash
git clone https://github.com/dagster-io/erk-statusline
cd erk-statusline
uv sync
```

## Usage

Add to `~/.claude/settings.json`:

```json
{
  "statusLine": {
    "type": "command",
    "command": "erk-statusline"
  }
}
```

## Debugging

The statusline writes debug logs to help diagnose issues like missing `chks:` indicator, timeouts, or API failures.

**Log location:** `~/.erk/logs/statusline/<session-id>.log`

**To view logs for your current session:**

```bash
# Find recent logs
ls -lt ~/.erk/logs/statusline/ | head

# Tail the most recent log
tail -f ~/.erk/logs/statusline/$(ls -t ~/.erk/logs/statusline/ | head -1)
```

**Example log output:**

```
2025-01-05 12:34:56 DEBUG Statusline invoked: session=abc123 cwd=/path/to/repo
2025-01-05 12:34:56 DEBUG Fetching GitHub data for branch=feature-branch
2025-01-05 12:34:56 DEBUG Fetching PR details: owner/repo #4225
2025-01-05 12:34:56 DEBUG Fetching check runs: owner/repo sha=abc1234
2025-01-05 12:34:57 DEBUG PR details fetched: owner/repo #4225 in 0.8s -> MERGEABLE
2025-01-05 12:34:57 DEBUG Check runs fetched: owner/repo sha=abc1234 in 0.9s -> 5 checks
2025-01-05 12:34:57 DEBUG Final result: branch=feature-branch pr=4225 checks=🔄
```

**Common issues to look for:**

- **Timeout messages** - API calls taking too long (default timeout: 1.5s per call)
- **Empty checks** - `Final result: ... checks=(empty)` means no check runs were returned
- **Cache behavior** - Look for "Cache hit/miss" messages to understand caching

## Development

```bash
# Run all checks (lint, typecheck, tests)
make check

# Run individual checks
make lint
make typecheck
make test

# Run tests with coverage
make test-coverage
```
erk-shared 0.7.4
Shared utilities and interfaces for erk and erk-kits
Requires Python: >=3.11

# erk-shared

Shared utilities and interfaces for erk and erk-kits packages.

This package provides:

- **GitHub Issues Interface**: ABC with Real/Fake implementations
- **Naming Utilities**: Filename and worktree name transformations
- **Metadata Blocks**: GitHub comment formatting utilities
- **Impl Folder Utilities**: Issue reference management and progress parsing

## Purpose

This package exists to break the circular dependency between `erk` and `erk-kits`:

- `erk` imports kit utilities from `erk-kits`
- `erk-kits` imports interfaces and utilities from `erk`

By extracting shared code to `erk-shared`, we create an acyclic dependency graph:

```
erk-shared (no dependencies)
    ↑
    |
erk-kits (depends on: erk-shared)
    ↑
    |
erk (depends on: erk-kits, erk-shared)
```

## Note

This is an internal workspace package, not published to PyPI.