Troubleshooting

This page collects common problems and possible fixes.

If something is still unclear after reading this page, ask for help on GitHub or Discord.

See also: FAQ, Developer handbook

Python command not found

Try:

python3 --version

or:

py --version

If none of these work, Python may not be installed or may not be added to your system path.

Virtual environment will not activate

Make sure the virtual environment exists:

python -m venv .venv

On Linux or macOS:

source .venv/bin/activate

On Windows PowerShell:

.venv\Scripts\Activate.ps1

If PowerShell blocks activation, your execution policy may need to be changed. Ask for help if you are unsure.

Ruff command not found

Make sure your virtual environment is active.

Then install requirements:

pip install -r requirements.txt

Try again:

ruff check .

App does not start

Check that:

• you are inside the project folder
• your virtual environment is active
• requirements are installed
• you are running python -m pynventory.main from the repository root

If the app prints an error, copy the full error message when asking for help.

data/products.db appears as modified

The app uses a local SQLite database file named data/products.db.

Running the app may change this file.

The data/ folder is tracked with data/.gitkeep, but data/products.db is local development data.

Do not include data/products.db in your pull request.

Before committing, check:

git status

If data/products.db appears, leave it unstaged.

I committed the wrong file

If you accidentally staged a file but have not committed yet, unstage it:

git restore --staged data/products.db

If you already committed, ask for help before trying to fix Git history.

I am on the wrong branch

Check your current branch:

git branch

The current branch has a * next to it.

To switch branches:

git checkout branch-name

If you have uncommitted work, Git may stop you from switching branches. Ask for help if you are unsure what to do.

Pull request has no linked issue

Pull requests should link to an issue.

In the pull request description, include:

Closes #12

Replace 12 with the correct issue number.

My branch is behind master

If your branch is behind master, first make sure your work is committed.

Then ask for help if you are not comfortable updating your branch yet.

Keeping branches up to date is normal, but it is better to ask than accidentally lose work.

I am stuck

Being stuck is part of learning.

When asking for help, include:

• what you were trying to do
• what command you ran
• what happened
• what you expected to happen
• any error message you saw

Clear questions are easier to answer.