Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-4088GitHub issuePublicReceived

Complete Guide for Python venv setup

Reported by vitalune · filed Feb 3, 2026Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Complete Guide for Python venv setuprevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.3.3, Linux 6.18.3, Hyprland 0.53.1, Alacritty 0.16.1

What's wrong?

Python Virtual Environment Setup for Omarchy

Closes/Related to #3156

Omarchy's Starship prompt overrides Python's default venv indicator, and the activation script returns exit code 1 (showing ✗ instead of ❯).
this really bothered me as a python dev so i configured my own setup and decided to share it here.

Quick Setup

1. Add Python module to Starship

Edit ~/.config/starship.toml:

# Add $python to your format line:
format = "[$directory$git_branch$git_status$python]($style)$character"

# Add at end of file:
[python]
symbol = "🐍 "
pyenv_version_name = true
format = 'via [${symbol}${pyenv_prefix}(${version} )(\($virtualenv\) )]($style)'
style = "bold yellow"
pyenv_prefix = "pyenv "
python_binary = ["python3", "python", "python2"]
detect_extensions = ["py"]
detect_files = [".python-version", "Pipfile", "pyproject.toml", "requirements.txt", "setup.py", "tox.ini"]
detect_folders = []
disabled = false

2. Add helpers to ~/.bashrc

# Create venv with fixed exit code
mkv() {
    python -m venv .venv && \
    echo -e "\nreturn 0" >> .venv/bin/activate && \
    echo "✓ Created .venv"
}

# Smart activation (prevents double-activation)
alias va='[ -z "$VIRTUAL_ENV" ] && source .venv/bin/activate || echo "Already active: $VIRTUAL_ENV"'

3. Reload shell

source ~/.bashrc

Usage

mkv        # Create venv
va         # Activate
deactivate # Deactivate

Result

# Before
[folder-name] main ✗           # No indicator, wrong symbol

# After  
[folder-name] main (.venv) ❯   # Clear indicator, correct symbol

Demo

<img width="1000" height="435" alt="Image" src="https://github.com/user-attachments/assets/0b5cd4d7-23f8-427c-a13b-ea5d6bcb3824" />

View raw text
### System details

Omarchy 3.3.3, Linux 6.18.3, Hyprland 0.53.1, Alacritty 0.16.1

### What's wrong?

# Python Virtual Environment Setup for Omarchy

> Closes/Related to #3156

Omarchy's Starship prompt overrides Python's default venv indicator, and the activation script returns exit code 1 (showing `✗` instead of `❯`). 
this really bothered me as a python dev so i configured my own setup and decided to share it here.

## Quick Setup

### 1. Add Python module to Starship

Edit `~/.config/starship.toml`:

```toml
# Add $python to your format line:
format = "[$directory$git_branch$git_status$python]($style)$character"

# Add at end of file:
[python]
symbol = "🐍 "
pyenv_version_name = true
format = 'via [${symbol}${pyenv_prefix}(${version} )(\($virtualenv\) )]($style)'
style = "bold yellow"
pyenv_prefix = "pyenv "
python_binary = ["python3", "python", "python2"]
detect_extensions = ["py"]
detect_files = [".python-version", "Pipfile", "pyproject.toml", "requirements.txt", "setup.py", "tox.ini"]
detect_folders = []
disabled = false
```

### 2. Add helpers to `~/.bashrc`

```bash
# Create venv with fixed exit code
mkv() {
    python -m venv .venv && \
    echo -e "\nreturn 0" >> .venv/bin/activate && \
    echo "✓ Created .venv"
}

# Smart activation (prevents double-activation)
alias va='[ -z "$VIRTUAL_ENV" ] && source .venv/bin/activate || echo "Already active: $VIRTUAL_ENV"'
```

### 3. Reload shell

```bash
source ~/.bashrc
```

## Usage

```bash
mkv        # Create venv
va         # Activate
deactivate # Deactivate
```

## Result

```
# Before
[folder-name] main ✗           # No indicator, wrong symbol

# After  
[folder-name] main (.venv) ❯   # Clear indicator, correct symbol
```

## Demo

<img width="1000" height="435" alt="Image" src="https://github.com/user-attachments/assets/0b5cd4d7-23f8-427c-a13b-ea5d6bcb3824" />
  • 0b5cd4d7-23f8-427c-a13b-ea5d6bcb3824

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.