ofek / ofek/pyapp

how to manage old installations

Open
#205 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2k
Forks
65
PR merge metrics
No merged PRs in 30d

Description

I'm giving pyapp a try for a new project. So far I like the simplicity, however how do you manage old installations. If I bump the version number I see that pyapp creates a new venv with that version number. Once I've overwritten the old binary I don't see an automated way to remove the old venv. How do i manage old venv's without having to remember to remove them before updating the executable.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by tracing pyapp's update flow and how versioned virtual environments are created and retained; define what counts as an obsolete environment, then verify that updating an executable cleans up old environments without removing the active one.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.