Skip to content

README.md

Latest commit

 

History

History
78 lines (65 loc) · 2.78 KB

README.md

File metadata and controls

78 lines (65 loc) · 2.78 KB
Raw

SecureVoiceSystem — Quickstart

This repository contains a skeleton SecureVoiceSystem project with gui/, core/, and data/ folders. This README explains how to create and use a Python virtual environment on Windows and run the project stubs.

Project root (example): c:\Users\DELL\Desktop\SecureVoiceSystem

Prerequisites

  • Python 3.8+ installed. If python --version fails, try py -3 --version or install from https://python.org and enable "Add Python to PATH".

1) Create a virtual environment Run these commands from the project root (c:\Users\DELL\Desktop\SecureVoiceSystem). Use one of the two options below depending on which Python launcher you prefer.

Using python:

python -m venv .venv

Or using the Windows Python launcher:

py -3 -m venv .venv

This creates a .venv folder in the project root.

2) Activate the virtual environment

  • PowerShell (recommended if you use PowerShell):
# If you see an execution policy error, see the Troubleshooting section below
.\.venv\Scripts\Activate.ps1
  • Command Prompt (cmd.exe):
.\.venv\Scripts\activate

Once activated, your prompt should show (.venv) as a prefix.

3) Upgrade pip (optional but recommended)

python -m pip install --upgrade pip

4) Install dependencies With the venv active and your working directory at the project root:

pip install -r requirements.txt

5) Run the project stub While the venv is active:

python main.py

You should see console output similar to:

Launching GUI stubs (sender, receiver, middleman)
Sender GUI starting (stub)
Receiver GUI starting (stub)
Middleman GUI starting (stub)

6) Deactivate the virtual environment

deactivate

Troubleshooting

  • "python" not found: Use py -3 or reinstall Python and select "Add to PATH".
  • Activation blocked in PowerShell (execution policy): Run PowerShell as Administrator and execute:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Then re-run .\.venv\Scripts\Activate.ps1. If you prefer not to change execution policy, use the cmd.exe activation instead.

  • pip install issues (compiling wheels / build tools): If a package fails to build, copy the error and I can help. Installing build-tools or using wheels from PyPI often solves native build failures.

Next steps I can do for you

  • Create the venv locally in the repository (I cannot run commands on your machine, but I can generate a PowerShell or batch script for you to run).
  • Implement a real crypto_utils using pycryptodome and a verified AES-HMAC pattern.

If you want the script to create/activate/install automatically, tell me which shell you prefer (PowerShell or cmd) and I will add a ready-to-run script.